| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marius Mauch wrote: |
| 5 |
> On Wed, 10 Oct 2007 10:16:03 +0200 |
| 6 |
> "Denis Dupeyron" <calchan@g.o> wrote: |
| 7 |
> |
| 8 |
>> On 10/10/07, Zac Medico <zmedico@g.o> wrote: |
| 9 |
>>> I think it's OK to start using package.use now considering that |
| 10 |
>>> package.use has been supported since portage-2.1.2 and that's been |
| 11 |
>>> stable since February. There are already a couple of packages using |
| 12 |
>>> it in the tree now. |
| 13 |
>> Is it a good idea for those ebuilds that require new features to have |
| 14 |
>> a >= dependency on a specific version of portage ? Or not ? |
| 15 |
> |
| 16 |
> No, as it wouldn't help anyway: the depgraph is calculated before |
| 17 |
> portage would be updated (so package.use/IUSE defaults wouldn't be |
| 18 |
> used). |
| 19 |
|
| 20 |
Results may vary if the user doesn't manually upgrade portage before |
| 21 |
doing other upgrades. After portage upgrades itself it will exec |
| 22 |
emerge --resume if there are remaining packages in the merge list. |
| 23 |
Like you said, the new version of portage will not recalculate |
| 24 |
dependencies when it resumes, but it will recalculate USE flags |
| 25 |
(bugs #183683). It's inconsistent, which is one reason why the |
| 26 |
recommended practice is to upgrade portage alone before attempting |
| 27 |
to do additional updates. Eventually I'd like to add an option that |
| 28 |
behaves similar to --resume but also recalculates dependencies. |
| 29 |
|
| 30 |
Zac |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 33 |
|
| 34 |
iD8DBQFHDQwB/ejvha5XGaMRAr2FAJ9E0OtHnzKO+fYRahsqR6W13AYzvwCggIIi |
| 35 |
BqHtFv3zbFKoYj5bR7heK9k= |
| 36 |
=SaBU |
| 37 |
-----END PGP SIGNATURE----- |
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives