| Re: [AD] grabber.txt moved => bug |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> > > > Any thoughts on this? As far as I can see, the grabber
> > > > can't actually make any assumptions about where to find
> > > > grabber.txt. Personally, I certainly don't run it from a
> > > > location where it will find ../docs/txt/grabber.txt... I
> > > > think we should restore the old behavior in the sense that
> > > > grabber.txt is also copied to the tools directory. We can
> > > > then tell the user that s/he has to place the grabber.txt
> > > > file in the same directory as the executable if s/he attempts
> > > > to move it (although we should not put it in /usr/local/bin
> > > > ourselves).
Allegro could try to be a good unix citizen and install
the grabber.txt in some /usr/share directory or whatever the
standard says. Then we can use set_allegro_resource_path() and
find_allegro_resource to satisfy the loading bit.
> > > What about a config entry "[grabber]docs_path"? After all,
> > > we already have a section [grabber], so why not put it to
> > > some good use. [...]
That's another possible one, though 95% users shouldn't need it if
the former is performed correctly.
Is there a patch for any of those two solutions?