On Fri, 2007-10-12 at 22:47 +0530, S h i v wrote:
> Inputs below
> - some of these might be already present that I am not aware of.
> - couple of them are not true feature enhancements but better
> defaults, stricter error checks.
Great feedback and some of them are 5-minute jobs, thanks!
> [1] Mechanism to provide dependency information in the OR form.
> OSOLgtk2 OR CSWgtk2 OR SUNWgtk2
There's an RFE with a patch in the sourceforge tracker for
supporting "Requires: /path/to/file" type of dependencies.
So instead of an "OR" thingie, you could write:
Requires: /usr/lib/libgtk-x11-2.0.so
then pkgbuild will check which package it belongs to and
puts it in the depend file.
It doesn't help if the file can be in different locations,
but I don't think it's good idea to mix and match libs
from different locations anyway.
[some good ideas deleted]
> [6] ("exclude" modifier listed in the enhancements considered is
> probably this)
It is. Recent versions of RPM support this. If you use the
%exclude modifier in the %files list it means this file should
not be included in the package.
> Addendum: Allowing the spec author to specify a <file-name> under
> %files section. This <file-name> specified can have exact list of
> files to be installed (something like the install file in ON)
This is already supported:
%files -f foo.lst
foo.lst has to be in the source directory and may be created
by the build itself. The mozilla build in S10 uses this feature.
Thanks,
Laca
