| 1 |
I reported a bug earlier today that turned out to be caused by a |
| 2 |
slightly older version of Portage. Shouldn't we consider having portage |
| 3 |
or the ebuilds handle this type of situation better, by either having |
| 4 |
the ebuilds have a particular version of portage as a dependency or |
| 5 |
making portage always check for a newer stable version of portage |
| 6 |
whenever it does an emerge and then upgrading to that first. As this |
| 7 |
might be "bad" behaviour for some people under certain circumstances, it |
| 8 |
could always be enabled or disabled via a switch like --upportage or |
| 9 |
some such. |
| 10 |
|
| 11 |
Does anyone see a good solution here? If you should always be using the |
| 12 |
newest portage then shouldn't portage check that its' self? |
| 13 |
|
| 14 |
Thanks, |
| 15 |
Sean |
| 16 |
|
| 17 |
-- |
| 18 |
gentoo-dev@g.o mailing list |
Archives