I tried that but it would require hard-coding the binary version in ports Makefile. I think cleaner way is to just add note in package to run 'chicken-install' manually.
Timo On Tue, Jul 1, 2014 at 7:14 AM, Felix Winkelmann < [email protected]> wrote: > > "Warning: cannot run `chicken-install update-db' when cross-compiling or > > DESTDIR is set" > > > > So that step is skipped as ports infrastructure uses the DESTDIR > argument. > > I've digged a bit further and update-db seems to generate modules.db file > > in /usr/local/lib/chicken/7 directory. > > > > How is this file used? > > My main problem is to determine if the warning can be skipped and users > be > > instructed to run 'chicken-install -update-db' manually themselves. > > Or the port could easily be patched to simply disregard the check and run > > the chicken-install -update-db even with DESTDIR. > > I'm not 100% sure, but you could try to disable the check and set the > environment-variable CHICKEN_REPOSITORY during the invocation of > "chicken-install -update-db" to the correct directory (probably > $DESTDIR/lib/chicken/7 ?) > > > felix >
_______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
