FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 10-08-2011, 05:51 PM
Дмитрий Матросов
 
Default debian/rules binary and build target dependencies clarification

2011/10/7 Bernhard R. Link <brlink@debian.org>:
> * Дмитрий Матросов <sgf.dma@gmail.com> [111007 16:27]:
>> But in the section 7.7 of Debian policy manual:
>> > clean, build-arch, and binary-arch
>> > Only the Build-Depends and Build-Conflicts fields must be satisfied when
>> > these targets are invoked.
>> > build, build-indep, binary, and binary-indep
>> > The Build-Depends, Build-Conflicts, Build-Depends-Indep, and
>> > Build-Conflicts-Indep fields must be satisfied when these targets are
>> > invoked.
>>
>> And footnote 55:
>> > Anyone building the build-indep and binary-indep targets is assumed to be
>> > building the whole package, and therefore installation of all build
>> > dependencies is required.
>>
>> So, as i understand, in this case dependencies will look like
>>
>> binary : binary-arch binary-indep
>> binary-indep : build-indep build-arch <----?
>
> What you write here looks like makefile dependencies, i.e. like
> something written in debian/rules. In that sense it is obviously
> wrong. Nothing says you must have called build-arch to be able
> to run build-indep or binary-indep.
>
> All it says is that people are not required to add things to
> "Build-Depends-Indep:" which are already in "Build-Depends:".

So, this means that there is no strict relationship between content of
Build-Depends-* field and build-* target dependencies like:
"'Build-Depends' field contains all dependencies for 'build-arch' target
and nothing more", or "'Build-Depends-Indep' contains all dependencies
for 'build-indep' target and nothing more". Am i understand you correctly?

> P.S: Note that currently Build-Depends-Indep is not working as
> Debian is stalled in a decade old dream for a technical solution,
> so one has to put everything in Build-Depends anyway...

Well, i just want to understand theory


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAFdVUFm4RHnwDT9--ZYdsL09KTQkfosKzXiT38kc9_uCwN_k9A@mail.gmail.com"> http://lists.debian.org/CAFdVUFm4RHnwDT9--ZYdsL09KTQkfosKzXiT38kc9_uCwN_k9A@mail.gmail.com
 
Old 10-10-2011, 08:00 AM
Thibaut Paumard
 
Default debian/rules binary and build target dependencies clarification

Hi,

Le 08/10/11 19:51, Дмитрий Матросов a écrit :

>
> So, this means that there is no strict relationship between content of
> Build-Depends-* field and build-* target dependencies like:
> "'Build-Depends' field contains all dependencies for 'build-arch' target
> and nothing more", or "'Build-Depends-Indep' contains all dependencies
> for 'build-indep' target and nothing more". Am i understand you correctly?
>

The idea is that architecture independent packages are not always built
(actually, I believe they are _never_ automatically built, since they
come with the source upload, and whatever binary package is uploaded
with the source package is not rebuilt!)

So Build-Depends-Indep should list those dependencies which only need to
be installed to build the arch-indep packages, so that in the real-world
situation where only the arch packages are built, those dependencies are
not uselessly installed.

On the other hand, there is no real-world use case to build _only_
arch-indep packages, without the arch packages. So both build-arch and
build-indep can count on anything listed in Build-Depends.

The theory (and I'm not sure of how it currently works in practice) is
that the autobuilders, most of the time, install only Build-Depends on
call only binary-arch. On the developer's machine however (or on a full
rebuild), both Build-Depends and Build-Depends-Indep are installed, and
both binary-arch and binary-indep are called.

Regards, Thibaut.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E92A605.2010703@free.fr">http://lists.debian.org/4E92A605.2010703@free.fr
 
Old 10-10-2011, 08:00 AM
Thibaut Paumard
 
Default debian/rules binary and build target dependencies clarification

Hi,

Le 08/10/11 19:51, Дмитрий Матросов a écrit :

>
> So, this means that there is no strict relationship between content of
> Build-Depends-* field and build-* target dependencies like:
> "'Build-Depends' field contains all dependencies for 'build-arch' target
> and nothing more", or "'Build-Depends-Indep' contains all dependencies
> for 'build-indep' target and nothing more". Am i understand you correctly?
>

The idea is that architecture independent packages are not always built
(actually, I believe they are _never_ automatically built, since they
come with the source upload, and whatever binary package is uploaded
with the source package is not rebuilt!)

So Build-Depends-Indep should list those dependencies which only need to
be installed to build the arch-indep packages, so that in the real-world
situation where only the arch packages are built, those dependencies are
not uselessly installed.

On the other hand, there is no real-world use case to build _only_
arch-indep packages, without the arch packages. So both build-arch and
build-indep can count on anything listed in Build-Depends.

The theory (and I'm not sure of how it currently works in practice) is
that the autobuilders, most of the time, install only Build-Depends on
call only binary-arch. On the developer's machine however (or on a full
rebuild), both Build-Depends and Build-Depends-Indep are installed, and
both binary-arch and binary-indep are called.

Regards, Thibaut.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E92A605.2010703@free.fr">http://lists.debian.org/4E92A605.2010703@free.fr
 
Old 10-10-2011, 08:00 AM
Thibaut Paumard
 
Default debian/rules binary and build target dependencies clarification

Hi,

Le 08/10/11 19:51, Дмитрий Матросов a écrit :

>
> So, this means that there is no strict relationship between content of
> Build-Depends-* field and build-* target dependencies like:
> "'Build-Depends' field contains all dependencies for 'build-arch' target
> and nothing more", or "'Build-Depends-Indep' contains all dependencies
> for 'build-indep' target and nothing more". Am i understand you correctly?
>

The idea is that architecture independent packages are not always built
(actually, I believe they are _never_ automatically built, since they
come with the source upload, and whatever binary package is uploaded
with the source package is not rebuilt!)

So Build-Depends-Indep should list those dependencies which only need to
be installed to build the arch-indep packages, so that in the real-world
situation where only the arch packages are built, those dependencies are
not uselessly installed.

On the other hand, there is no real-world use case to build _only_
arch-indep packages, without the arch packages. So both build-arch and
build-indep can count on anything listed in Build-Depends.

The theory (and I'm not sure of how it currently works in practice) is
that the autobuilders, most of the time, install only Build-Depends on
call only binary-arch. On the developer's machine however (or on a full
rebuild), both Build-Depends and Build-Depends-Indep are installed, and
both binary-arch and binary-indep are called.

Regards, Thibaut.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E92A605.2010703@free.fr">http://lists.debian.org/4E92A605.2010703@free.fr
 
Old 10-10-2011, 03:27 PM
Дмитрий Матросов
 
Default debian/rules binary and build target dependencies clarification

Thanks a lot for the explanation.

2011/10/10 Thibaut Paumard <mlotpot.news@free.fr>:
> Hi,
>
> Le 08/10/11 19:51, Дмитрий Матросов a écrit :
>
>>
>> So, this means that there is no strict relationship between content of
>> Build-Depends-* field and build-* target dependencies like:
>> "'Build-Depends' field contains all dependencies for 'build-arch' target
>> and nothing more", or "'Build-Depends-Indep' contains all dependencies
>> for 'build-indep' target and nothing more". Am i understand you correctly?
>>
>
> The idea is that architecture independent packages are not always built
> (actually, I believe they are _never_ automatically built, since they
> come with the source upload, and whatever binary package is uploaded
> with the source package is not rebuilt!)
>
> So Build-Depends-Indep should list those dependencies which only need to
> be installed to build the arch-indep packages, so that in the real-world
> situation where only the arch packages are built, those dependencies are
> not uselessly installed.
>
> On the other hand, there is no real-world use case to build _only_
> arch-indep packages, without the arch packages. So both build-arch and
> build-indep can count on anything listed in Build-Depends.
>
> The theory (and I'm not sure of how it currently works in practice) is
> that the autobuilders, most of the time, install only Build-Depends on
> call only binary-arch. On the developer's machine however (or on *a full
> rebuild), both Build-Depends and Build-Depends-Indep are installed, and
> both binary-arch and binary-indep are called.
>
> Regards, Thibaut.
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/4E92A605.2010703@free.fr
>
>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CAFdVUFnVjVnaWCmdi7zHJGMLNVZW6EZ9u2xYvL8CuAX4_U1xc A@mail.gmail.com">http://lists.debian.org/CAFdVUFnVjVnaWCmdi7zHJGMLNVZW6EZ9u2xYvL8CuAX4_U1xc A@mail.gmail.com
 

Thread Tools




All times are GMT. The time now is 01:32 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org