2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> On May 5, 2008, at 6:48 AM, Marcin Kasperski wrote:
> >>> The point of this file was to make it possible to build scid
> >>> in Linux "packaged" way, where binaries and data are not
> >>> installed together, but we use sth like /usr/bin/scid (or
> >>> /usr/games/scid) and /usr/share/scid/data/....
> >>
> >> Given that books and bases directories are now user
> >> configurable, is it still useful to have this option ?
> >
> > IMO yes. It should be possible to compile scid with those
> > defaults - so if it is packaged, the user can run it succesfully
> > after installation.
> >
> Ah, sorry about that. The only reason I did it this way is that it
> seemed to accommodate the common case and I didn't want to go ripping
> into the configuration script. There needs to be a way to handle both
> cases but for OS X, it needs to be determined at runtime for the
> default to work after installation. I'll give it a thought.
>
Maybe there are things I did not get, but I don't see the point in packaging
data and exec separately : I have some dependencies between data and some
features (training, books), and I'd prefer things to come in one simple
package. I don't think a package about 10 MB is too big.
Pascal
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
