On 21 Sep 2005, at 22:46, Daniel Macks wrote:


Currently, DocFiles takes a list of filenames (including shell
globbing), and allows renaming ("DocFiles:foo:bar" installs the file
"foo" from the source dir as "bar" in the doc dir). A fairly common
(in gnome at least) situation is that there is more than one file with
the same name (in different subdirs of the source), for example
ChangeLog and po/ChangeLog; we appear to use ChangeLog.po as a
standard renaming convention for the latter. Anyone object to adding
an implicit renaming mode that does this automatically? For example:

  DocFiles: foo:bar examples/* ChangeLog po/ChangeLog:

would (still) install foo as bar, but po/ChangeLog would automatically
be installed as ChangeLog.po...saves a lot of typing (and typos),
especially in things like gnome-games that has 22 ChangeLog files:)
While we're improving that field, vasi asks for the ability to pass
directory names, so one could pass "examples" and it would be
recursively installed (instead of the more limited "examples/*" that
only does globbing (not recursion) of simple files). Anything else we
need syntax-wise? Conditionals?


A) I have no complex examples in mind for DocFiles.
But I see no reason why it shouldn't be basically the same as for Files.

The fact that in those fields one can use backquotes gives a great deal of flexibility
_ that should "merge" well with any other improvements _ .
It is only hampered by the line-length, or the single-line restriction.
A natural question would be whether one could have scripts in those fields, _ ie
DocFiles: <<
#!/bin/sh -ev
....
<<

with the interpretation that it is the output which is fed to DocFiles
(ie, it is in fact "DocFiles: `/var/tmp/tmp.number.code`").

B) On an unrelated matter, it would be nice if DocFiles could specify
to install just a symlink to the docfiles of a dependent pkg (eg, %N- shlibs). It is not completely trivial, as it requires (for transition at least) to
overcome (eg by an appropriate PreInstScript) dpkg's refusal to replace
a dir by a symlink.
(
# du -s /sw/share/doc
1561367 /sw/share/doc
_ with probably a thousand copies of GNU's standard INSTALL file _
is not prohibitive, but still deserves a bit of attention..
And/or, one may want to keep in /sw/share/doc only genuine documentation,
and put all the rest in say /sw/share/legal _ where the user would be
free to install a symlink to /dev/null..
)

JF Mertens




-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to