| 1 |
> You know, I'd actually support a rather more abrupt transition, |
| 2 |
> where we announce that on a particular date all digest files are going |
| 3 |
> to be removed, thereby breaking any version of portage older than |
| 4 |
> portage-x.y.z. Many people would probably miss such a deadline, but |
| 5 |
> assuming that we also publicize how to download and unpack a portage |
| 6 |
> rescue tarball then I would think that the actual pain would be minimal. |
| 7 |
> (Indeed, we could even have a fix-portage.sh script in |
| 8 |
> /usr/portage/scripts that would do the downloading and unpacking, if we |
| 9 |
> wanted to be particularly nice.) Backwards compatibility is nice, but |
| 10 |
> I'd really rather not see good ideas take a year to fully be implemented |
| 11 |
> unless absolutely required. |
| 12 |
|
| 13 |
How about instead of letting people use tarballs, we kill the digests |
| 14 |
for every package except portage and it's deps. That way we will break |
| 15 |
the system and enforce an upgrade, but we will also give them an easy |
| 16 |
upgrade route. (I haven't looked at the GLEP so I don't know about |
| 17 |
manifest compatibility). |
| 18 |
-- |
| 19 |
gentoo-dev@g.o mailing list |
Archives