| 1 |
Walter Dnes wrote: |
| 2 |
> On Wed, Mar 13, 2013 at 09:16:07AM +0000, Neil Bothwick wrote |
| 3 |
>> On Wed, 13 Mar 2013 10:24:00 +0200, Alan McKinnon wrote: |
| 4 |
>> |
| 5 |
>>> A useful trick I use on my Gentoo test/dev vms is a defined set called |
| 6 |
>>> @tools. These all use a shared /etc/portage/ for consistency, so add bc |
| 7 |
>>> to the set and it is merged everywhere. This helps keep my world free of |
| 8 |
>>> clutter. |
| 9 |
>> I do a similar thing, I have a set called @base, the first thing I do |
| 10 |
>> after unpacking a stage 3 and setting up make.conf is emerge @base. It |
| 11 |
>> means I have everything I expect on a computer and also shortcuts some of |
| 12 |
>> the install steps. |
| 13 |
> How are the portage-2.2.0 alphas for stability/bugs (hopefully lack |
| 14 |
> thereof)? I see alpha163 and alpha166 available. |
| 15 |
> |
| 16 |
|
| 17 |
I added portage to the keyword file then masked the 9999 version a good |
| 18 |
long while back. I'm on sys-apps/portage-2.2.0_alpha166 and I have not |
| 19 |
had any troubles so far. Your mileage may vary tho. |
| 20 |
|
| 21 |
Dale |
| 22 |
|
| 23 |
:-) :-) |
| 24 |
|
| 25 |
-- |
| 26 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives