[gentoo-embedded] Re: building a gentoo uclibc system

[Ned Ludd]

On Tue, 2004-06-08 at 09:19, Peter S. Mazinger wrote:
> Hello!
>
> I am working on a clean gentoo-uclibc system, but some of the packages are
> too old and need too much patching to work w/ uclibc, so I need ~arch
> version. How can I enforce usage of some of the packages that are marked
> as ~arch to be used for uclibc overwriting the keyword ~arch w/ arch.
> I do not want to use generally ~arch, only for some of the packages, and I
> do not want to remark these packages to stable.

/etc/portage/package.keywords 
man 5 portage ; # should have all you need to know about this file.

> These changes should also work for bootstrap and catalyst stage building.
>


> How are you intending to handle uclibc, should it have a separate profile,
> like uclibc-arch-2004.x and hardened-uclibc-arch-2004.x? the embedded
> subdir is not ok for it (ex. virtual/glibc sys-libs/glibc)

At one point we had a profile for uclibc which worked most for the
stable tree where we are keeping the old 0.9.21 in stable till the
uclibc toolchain is resolved.

( subdir glibc what? ) glibc has no place in the embedded community.


> Should the '-doc' use flag not been honoured generally (not
> installing any docs, info pages, man pages)?

# If we are talking firmware you will want to set the 
FEATURES="nodoc noman noinfo"
# check out the dyn_preinst() function in your $ROOT/usr/sbin/ebuild.sh

# the USE (+|-)doc really only applies to some gtk-doc thing. 
# But over time it's evolved into it's own thing sorta..

What I'd like to see happen in due time is for us to take on a feature
set much like openembedded where packages are broken into components
such a pkg-bin pkg-dev pkg-doc.
(-bin contains the ELF's only) 
(-dev contains the include.h files)
(-doc contains man pages/documentation)

> P.S. please cc to me, I am not on the list
Well get on the list :)

> Thanks, Peter

-- 
Ned Ludd <solar@g.o>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer