On Feb 13, 2004, at 9:39 AM, Remi Mommsen wrote:
I prefer the here-doc structure for Depends and BuildDepends in fink packages, where each dependency (with possible alternatives) is on a separate line. For example
Depends: <<
x11,
giflib-shlibs | libungif-shlibs
<<
IMO this is much more readable than an endless line and it eases to track changes in cvs considerably. You see immediately which dependencies have changed.
How about recommending the use of here-doc structures for Depends and BuildDepends in the packaging manual?
This seems more about esthetics; on the other hand, as to the users'
ease of use, the one line format allows to immediately get the dependencies
of a set of packages by a command like " f_whch <pkgs>|xargs grep 'Depends:' "
(where f_whch _ 'fink which' _ outputs, for each listed pkg succesively, a line
with the full path to the exact info file fink would use for that pkg _ cf eg
http://article.gmane.org/gmane.os.apple.fink.devel/7304/match=
for such a script).
Similarly, to get the set of pkgs that eg still depend on gd a simple
egrep -rI '[, ]gd([, ]|$)' /sw/fink/dists/unstable|grep 'Depends:'
suffices with the 1 line convention.
(And as long as only a dozen pkgs don't follow that convention, it is still tolerable)
Is it really worthwhile to complicate so much such simple uses ???
Jean-Francois
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
