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