1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Chris Gianelloni wrote: |
5 |
> I do have one question, though. What does an older portage version do |
6 |
> when it hits a package with a missing digest file? |
7 |
> |
8 |
> Let's say I've got portage prior to 2007.0's, so it doesn't support |
9 |
> Manifest2 only. I want to "emerge --oneshot portage" to get to the |
10 |
> latest version. What do I need a digest on? Just portage? portage and |
11 |
> its dependencies? Which dependencies? All of them, or just the ones |
12 |
> I'll actually need to merge? |
13 |
> |
14 |
> I guess what I'm asking is if it is possible to have repoman create a |
15 |
> digest for sys-apps/portage only, for the slow upgraders. Of course, |
16 |
> this assumes its even possible on the portage side to bother. If not, |
17 |
> just ignore this part. |
18 |
> |
19 |
|
20 |
All that they have to do is run the manifest221 script [1] and it |
21 |
will generate the old style digest files containing SHA1 digests |
22 |
from the Manifest files. I've tested that script on a 2005.0 stage3 |
23 |
and I was able to upgrade it pretty smoothly. |
24 |
|
25 |
[1] http://www.gentoo.org/proj/en/portage/doc/converting-manifest2.xml |
26 |
|
27 |
-----BEGIN PGP SIGNATURE----- |
28 |
Version: GnuPG v2.0.7 (GNU/Linux) |
29 |
|
30 |
iD8DBQFHnUIw/ejvha5XGaMRAi1XAJ9JE0aE9MwuSF+XRBi4SrMwFtkpxQCgpC2Z |
31 |
WEHpxtkRaquXWwLV34Nv8LI= |
32 |
=o11+ |
33 |
-----END PGP SIGNATURE----- |
34 |
-- |
35 |
gentoo-dev@l.g.o mailing list |