On Tue, Mar 29, 2005 at 08:50:36PM +0200, Andreas Barth wrote:
> * Adrian Bunk ([EMAIL PROTECTED]) [050329 19:35]:
> > If testing should make any sense, handling build dependencies as
> > dependencies in the testing scripts was required.
>
> We all know that your opinion about the usefulness of testing differes
> from the one the release team has. Please just accept this
> disagreement, and leave it at that. Thanks.
Was has this to do with the question whether testing handles
dependencies as build dependencies or not?
Facts:
You yourself have signed the announcement that removing two thirds of
the architectures from Debian releases was required since otherwise
release cycles on the order of 12-18 month weren't possible with the
testing release process. The release team agrees that the testing
release process is worth this removal.
You want to offer security support for testing (which is AFAIK the
reason why the sarge release is stalled since 7 months).
Security support can turn out to be a nightmare if build dependencies
aren't fulfilled.
Handling build dependencies as dependencies should be trivial in the
testing scripts and would only be in the spirit of testing.
Question:
Why don't you avoid all the possible problems for security support in
testing by handling build dependencies as dependencies?
> Cheers,
> Andi
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
