| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA256
|
| 3 |
|
| 4 |
On Mon, 7 Sep 2020 21:39:54 +1200
|
| 5 |
Kent Fredric <kentnl@g.o> wrote:
|
| 6 |
|
| 7 |
> On Mon, 7 Sep 2020 08:14:52 +0200 |
| 8 |
> Michał Górny <mgorny@g.o> wrote: |
| 9 |
> |
| 10 |
> > However, please |
| 11 |
> > + do not include it in the <c>package.mask</c> entry as users do |
| 12 |
> > not need |
| 13 |
> > + to be forced to proactively unmerge it. |
| 14 |
> |
| 15 |
> I can think of a utilitarian value of doing this anyway. |
| 16 |
> |
| 17 |
> Namely, it gives a window during `emerge -uD @world` where portage |
| 18 |
> tells you that they have a masked package installed, and the reason. |
| 19 |
|
| 20 |
I think portage also warns for installed packages with no corresponding
|
| 21 |
ebuild; the reason is somewhat generic though (sth like 'it is gone')
|
| 22 |
|
| 23 |
IMHO last rites windows have only one purpose: give time to people to
|
| 24 |
step up and fix the reason why it is going away
|
| 25 |
-----BEGIN PGP SIGNATURE-----
|
| 26 |
|
| 27 |
iHUEAREIAB0WIQSpOxaxaZikKNVNlsYOJUi7xgflrgUCX1YK/gAKCRAOJUi7xgfl
|
| 28 |
rrooAQCBK/WXgwMl1wm8jQh+e2oyD8WIAzSrzFFBCE7xWL1WGgEAgWSGBmG9ug8/
|
| 29 |
ZNfrHnOhBL2o6hZupzMy/84dX7DFBvk=
|
| 30 |
=pwzN
|
| 31 |
-----END PGP SIGNATURE----- |
Archives