Package: dpkg-cross
Tags: + moreinfo
thanks
One method of doing this could be to let the site-wide config include
the user-specific config where it exists.
I'll be experimenting with this setup in emdebian-tools.
>From the original request, it would probably be more intuitive for
user to override system as the system file will always exist. Missing
options in the user config would simply inherit from the system config.
However, the real reason behind the bug report has been superseded by
the -X option supported by dpkg-cross since 1.38:
(from man dpkg-cross)
-X, --exclude Removes the specified package from the dependencies of
the current package. Typically used to drop dependencies on
packages that are not required within a cross-build environment, e.g.
packages containing only executables or architecture independent
files.
dpkg-cross can only check the current package and
information about a dependency is not available. By default,
dpkg-cross converts all dependencies to specify the cross version of
the dependency package. If you know that a particular dependency should
not be converted (it provides no useful files or is architecture
independent), that dependency can be excluded and dpkg-cross will
remove that package from the dependency information.
-X|--exclude PACKAGE
needs to be repeated for each package to be excluded.
This allows a more fine-grained approach to excluding deps.
Note also that apt-cross uses this support to tell dpkg-cross to drop
Architecture:all dependencies.
So, is there still an issue to be resolved by this bug report?
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
Attachment:
pgp692jtkfKjD.pgp
Description: PGP signature