Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-05 Thread Kari Pahula
On Thu, Jan 05, 2006 at 11:23:43AM +0100, Bill Allombert wrote: > Before going farther, I strongly recommends you read the > bug log for #218893. Good to see that this has been discussed before. IMHO the sanest thing would be to make build-{arch,indep} goals mandatory. It would make build-arch t

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-05 Thread Adeodato Simó
* Kari Pahula [Wed, 04 Jan 2006 11:37:46 +0200]: > The reason why I got to think about this policy change was because I > noticed that every arch's buildd was calling my build-indep and having > doxygen generate 30 MBs of docs. I was suggested on IRC to either > generate the docs in binary-indep

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-05 Thread Bill Allombert
On Mon, Jan 02, 2006 at 11:44:21AM +0200, Kari Pahula wrote: > But, since it's not a requirement for debian/rules build-{arch,indep} > to return an error when the targets are missing, tools such as > dpkg-buildpackage have no choice but to always call debian-rules build > even when building arch de

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-04 Thread Kari Pahula
On Wed, Jan 04, 2006 at 01:56:13PM -0800, Russ Allbery wrote: > I just don't know how this sort of change fits into the policy process. How about this: change the policy to state that build-arch and build-indep should be present, make it a lintian warning if they're missing and defer any decision

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-04 Thread Kari Pahula
On Wed, Jan 04, 2006 at 10:30:04AM -0800, Russ Allbery wrote: > Kari Pahula <[EMAIL PROTECTED]> writes: > > > But all of the above are just implementation details. The important > > change would be to make it a requirement for build-{arch,indep} to be > > present. > > The difficulty with this so

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-04 Thread Russ Allbery
Kari Pahula <[EMAIL PROTECTED]> writes: > On Wed, Jan 04, 2006 at 10:30:04AM -0800, Russ Allbery wrote: >> The difficulty with this sort of change is that it requires changing >> every Debian package, or near to. I'm going to have the same problem >> with > As far as changes go, this one can be

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-04 Thread Russ Allbery
Kari Pahula <[EMAIL PROTECTED]> writes: > But all of the above are just implementation details. The important > change would be to make it a requirement for build-{arch,indep} to be > present. The difficulty with this sort of change is that it requires changing every Debian package, or near to.

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-04 Thread Kari Pahula
On Tue, Jan 03, 2006 at 02:34:45PM +, Ian Jackson wrote: > Kari Pahula writes ("Bug#345619: debian-policy: 4.8. binary-{arch, indep} > should fail with error code 2 -> must"): > > Debian policy 4.8. states: > > If one or both of the targets `build-arch' an

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-03 Thread Ian Jackson
Kari Pahula writes ("Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must"): > Debian policy 4.8. states: > If one or both of the targets `build-arch' and `build-indep' are > not provided, then invoking `debian/rules' with

Bug#345619: debian-policy: 4.8. binary-{arch, indep} should fail with error code 2 -> must

2006-01-02 Thread Kari Pahula
Package: debian-policy Version: 3.6.2.1 Severity: wishlist Debian policy 4.8. states: If one or both of the targets `build-arch' and `build-indep' are not provided, then invoking `debian/rules' with one of the not-provided targets as arguments should produce a exit status code of 2. I'm proposing