Dear Fink developers,
For some time now, 'fink validate' has attempted to enforce a (poorly-
documented) policy about scrollkeeper files: if a scrollkeeper file
is present, then the package should depend on scrollkeeper and
scrollkeeper-update should be called in postinstall and postremove
scripts.
There has been an objection to this from a fink developer who quite
reasonably points out that his package has documentation of all
sorts, including scrollkeeper files, but that one should not be
forced to install scrollkeeper to install his package. He found an
alternate solution for his scripts: if scrollkeeper-update is
present, then it is run.
Note that this solves the problem quite nicely, since scrollkeeper
itself runs scrollkeeper-update upon installation.
Do people agree that this is OK? We could even go further, and add a
fink declaration "UpdateScrollkeeper: true" analogous to "UpdatePOD:
true" which would let us put the requiste lines into the scripts
automatically. Good idea or not?
-- Dave
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
