What do you guys think of this idea? I think it's one of the smartest
I've heard for a while, and leaves open the possibility of further
extensions.
Another possibility is to have something like debian/rules.features,
which would have a list of features supported by the debian/rules
file. For example, current possible features, based on musings on the
-policy list, could include "build-arch" and "test".
For example, if debian/rules.features had one keyword per line, then
dpkg-buildpackage et al could do something like:
if [ -r debian/rules.features ] && grep -q build-arch debian/rules.features
then
...
else
...
fi
This would potentially be more flexible than debian/rules.version, but
also potentially more confusing.
----- Forwarded message from Bill Allombert <allomber@math.u-bordeaux.fr> -----
Date: Thu, 23 Oct 2003 00:58:19 +0200
From: Bill Allombert <allomber@math.u-bordeaux.fr>
Subject: Re: Bug#216492: FTBFS (unstable/all) missing build-dep
To: debian-policy@lists.debian.org
[...]
So I come up with a different proposal:
Introducing a new file, say debian/rules.version.
If this file does not exist, we declare that version=0,
else version=`cat debian/rules.version`.
Currently 2 versions are defined:
0: debian/rules support rules described as mandatory by policy.
1: as 0, but debian/rules also support build-arch and build-indep.
Future version of policy can define higher version.
dpkg-buildpackage just need to read this file before deciding
whether it can call debian/rules build-arch.
What do you think ?
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
----- End forwarded message -----
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, website: http://www.polya.uklinux.net/
Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/
Visit http://www.thehungersite.com/ to help feed the hungry