I'm installing uclibc-ng Gentoo on an old Atom netbook. I saw the
news item about uclibc-ng upgrade and wanted to do the switchover during
the install. This way "emerge -e @world" has to do "only" 153 packages
...3 times ...over ten hours each time on the ancient netbook. I
finished step 5, and need to do only...
> 6. Finally update uclibc-ng to the latest
>
> emerge =sys-libs/uclibc-ng-1.0.22
>
> 7. For good measure, rebuild the entire system
>
> emerge ?<80><94>e @world
uclibc-ng-1.0.22 is "masked by missing keywords"...
# grep KEYWORDS /usr/portage/sys-libs/uclibc-ng/uclibc-ng-1.0.22.ebuild
#KEYWORDS="-* ~amd64 ~arm ~mips ~ppc ~x86"
KEYWORDS=""
This is usually done for a reason. Are there any showstoppers with
uclibc-ng-1.0.22 and should I wait at uclibc-ng-1.0.20? Or is it OK to
tweak the ebuild and finish the upgrade?
--
Walter Dnes <waltdnes@waltdnes.org>
news item about uclibc-ng upgrade and wanted to do the switchover during
the install. This way "emerge -e @world" has to do "only" 153 packages
...3 times ...over ten hours each time on the ancient netbook. I
finished step 5, and need to do only...
> 6. Finally update uclibc-ng to the latest
>
> emerge =sys-libs/uclibc-ng-1.0.22
>
> 7. For good measure, rebuild the entire system
>
> emerge ?<80><94>e @world
uclibc-ng-1.0.22 is "masked by missing keywords"...
# grep KEYWORDS /usr/portage/sys-libs/uclibc-ng/uclibc-ng-1.0.22.ebuild
#KEYWORDS="-* ~amd64 ~arm ~mips ~ppc ~x86"
KEYWORDS=""
This is usually done for a reason. Are there any showstoppers with
uclibc-ng-1.0.22 and should I wait at uclibc-ng-1.0.20? Or is it OK to
tweak the ebuild and finish the upgrade?
--
Walter Dnes <waltdnes@waltdnes.org>