[gentoo-dev] Should we list sys-apps/sed in DEPEND

[gentoo-dev] Should we list sys-apps/sed in DEPEND

[Thomas Kahle]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

... if it is used in the ebuild?

It is a system package here on amd64, but is it everywhere?

Cheers,
Thomas

-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Markos Chandras]

On 19 February 2013 13:10, Thomas Kahle <tomka@gentoo.org> wrote:
> ... if it is used in the ebuild?
>
> It is a system package here on amd64, but is it everywhere?
>
> Cheers,
> Thomas
>
> --
> Thomas Kahle
> http://dev.gentoo.org/~tomka/

No you should not. It is a system package for every arch because it's
listed in base/packages so every arch should have it.

-- 
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Ralph Sennhauser]

[-- Attachment #1: Type: text/plain, Size: 321 bytes --]

On Tue, 19 Feb 2013 14:10:33 +0100
Thomas Kahle <tomka@gentoo.org> wrote:

> ... if it is used in the ebuild?
> 
> It is a system package here on amd64, but is it everywhere?
> 
> Cheers,
> Thomas
> 

Gnu sed version 4 is guaranteed by pms [1]

[1] http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-12500011.3.1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Dennis Lan (dlan)]

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Hi thomas, @all:
  Thanks for bring up this for discussion..
  I think 'embedded' profile have only one sys-apps/busybox as system
package,
but seems this profile haven't updated for long time, and may become
obsolete..

Dennis

On Tue, Feb 19, 2013 at 9:10 PM, Thomas Kahle <tomka@gentoo.org> wrote:

> ... if it is used in the ebuild?
>
> It is a system package here on amd64, but is it everywhere?
>
> Cheers,
> Thomas
>
> --
> Thomas Kahle
> http://dev.gentoo.org/~tomka/
>

[-- Attachment #2: Type: text/html, Size: 904 bytes --]

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 324 bytes --]

On Tue, 19 Feb 2013 14:10:33 +0100
Thomas Kahle <tomka@gentoo.org> wrote:

> ... if it is used in the ebuild?
> 
> It is a system package here on amd64, but is it everywhere?

No. sed is required by POSIX, so it shall always be there.

Additionally, it's provided by PMS too.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Brian Dolbec]

On Tue, 2013-02-19 at 14:10 +0100, Thomas Kahle wrote:
> ... if it is used in the ebuild?
> 
> It is a system package here on amd64, but is it everywhere?
> 
> Cheers,
> Thomas
> 

Only if the pkg is also a system package.  I recently ran into a problem
running a catalyst build because portage-utils did not list the xz-utils
dep which was another system package.  It failed to unpack because
xz-utils was still waiting to be merged.  I was running catalyst with
--jobs=3.

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Christoph Junghans]

2013/2/19 Brian Dolbec <dolsen@gentoo.org>:
> On Tue, 2013-02-19 at 14:10 +0100, Thomas Kahle wrote:
>> ... if it is used in the ebuild?
>>
>> It is a system package here on amd64, but is it everywhere?
>>
>> Cheers,
>> Thomas
>>
>
> Only if the pkg is also a system package.  I recently ran into a problem
> running a catalyst build because portage-utils did not list the xz-utils
> dep which was another system package.  It failed to unpack because
> xz-utils was still waiting to be merged.  I was running catalyst with
> --jobs=3.
That is what unpacker_src_uri_depends from unpacker.eclass is intended for.
DEPEND+=$(unpacker_src_uri_depends)

>
>



--
Christoph Junghans
http://dev.gentoo.org/~ottxor/

Re: [gentoo-dev] Should we list sys-apps/sed in DEPEND

[Zac Medico]

On 02/19/2013 07:21 AM, Brian Dolbec wrote:
> On Tue, 2013-02-19 at 14:10 +0100, Thomas Kahle wrote:
>> ... if it is used in the ebuild?
>>
>> It is a system package here on amd64, but is it everywhere?
>>
>> Cheers,
>> Thomas
>>
> 
> Only if the pkg is also a system package.  I recently ran into a problem
> running a catalyst build because portage-utils did not list the xz-utils
> dep which was another system package.  It failed to unpack because
> xz-utils was still waiting to be merged.  I was running catalyst with
> --jobs=3.

If it's not in $PORTDIR/profiles/default/linux/packages.build then it's
not necessarily included in stage1 and therefore you can't rely on it
for stage1 -> stage2 -> stage3. If that's the case, then it has to be in
*DEPEND for anything in stage3.
-- 
Thanks,
Zac