Hamish Moffatt <[EMAIL PROTECTED]> writes:
> On Tue, Feb 22, 2005 at 07:52:57AM +0100, Ingo Juergensmann wrote:
>> On Tue, Feb 22, 2005 at 02:29:33PM +1100, Hamish Moffatt wrote:
>> > Why do the build servers install all the dependencies only to find out
>> > that some installed versions are insufficient for the build?
>>
>> Because the current buildd system is outdated in the meanwhile. It should be
>> replaced by a new framework.
>>
>> > Surely this can be determined _before_ installing the dependencies?
>> > No new information is available after install that wasn't available
>> > before.
>>
>> Bastian Blank worked on a database that handles all these build-deps on the
>> central wanna-build replacement. The idea is to give out just those packages
>
> Even that sounds too complicated. Really, each buildd can work this out
> on its own. Given the current packages files, determine whether you can
> meet all the dependencies.
>
> I think 'apt-get build-dep' does exactly this.
'apt-get build-dep' can't handle virtual packages reliably. Everything
with a Build-Depends: automaken will fail and many many more. Even
virtual packages with only one provider fail if there are multiple
sources for the package (different builds or versions).
The first one is a bug (current unwritten policy) in the package while
the later has a patch in BTS. So it wouldn't be unsurmountable obstacles.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
