After a few years of masking, we will finally remove support for USE=kdeprefix
from all KDE ebuilds/eclasses on or about 2011-06-06, moving everyone to the
recommended FHS layout. The attached news item meant to serve as an early
warning to affected users.

I plan to commit this news item on 2011-05-22 to give about 2 weeks warning to
users.

Please comment and review.
--
Jonathan CallenTitle: Removal of kdeprefix support
Author: Jonathan Callen <abcd@gentoo.org>
Content-Type: text/plain
Posted: 2011-05-22
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: kde-base/kdelibs[kdeprefix]

On 2011-06-06, kdeprefix support will be removed from all KDE ebuilds in
portage. After this is done, only one version of KDE SC will be able to
be installed at a time on a system. If you are currently using
USE=kdeprefix to install multiple versions of KDE SC simultaneously, you
will need to migrate to a non-kdeprefix installation.

To migrate, you will need to set USE=-kdeprefix (or remove the manual
unmasking of that flag in /etc/portage/profile) and rebuild all of the
installed packages in kde-base/. To reinstall these packages, you can
run: emerge --oneshot $(qlist -IC kde-base/)

>>>>> On Wed, 18 May 2011, Jonathan Callen wrote:

> Display-If-Installed: kde-base/kdelibs[kdeprefix]

I don't think that USE dependencies (or any other EAPI specific
features) are allowed here.

> run: emerge --oneshot $(qlist -IC kde-base/)

Is it guaranteed that your users have portage-utils installed?
Otherwise the qlist command may not be available.

Ulrich

On Wed, May 18, 2011 at 11:58 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Wed, 18 May 2011, Jonathan Callen wrote:
>
>> Display-If-Installed: kde-base/kdelibs[kdeprefix]
>
> I don't think that USE dependencies (or any other EAPI specific
> features) are allowed here.

You should file a bug about that; I'm sure one of the portage guys can
change the crap code I wrote 4 years ago to use the normal dependency
checking code for installed atoms.

-A

>
>> run: emerge --oneshot $(qlist -IC kde-base/)
>
> Is it guaranteed that your users have portage-utils installed?
> Otherwise the qlist command may not be available.
>
> Ulrich
>
>

>>>>> On Thu, 19 May 2011, Alec Warner wrote:

> You should file a bug about that; I'm sure one of the portage guys
> can change the crap code I wrote 4 years ago to use the normal
> dependency checking code for installed atoms.

But we wouldn't know if users have the updated portage version
installed, so it doesn't help for the current news item.

I think for a proper solution we would have to increase the number of
the News-Item-Format. Maybe even add a new header field for the EAPI.

Ulrich

On Thu, 19 May 2011 09:15:40 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> I think for a proper solution we would have to increase the number of
> the News-Item-Format. Maybe even add a new header field for the EAPI.

Could just use an 'eapi' file in the news directory. Although does
Portage support that?

--
Ciaran McCreesh

Ulrich Mueller wrote:

>>>>>> On Wed, 18 May 2011, Jonathan Callen wrote:
>
>> Display-If-Installed: kde-base/kdelibs[kdeprefix]
>
> I don't think that USE dependencies (or any other EAPI specific
> features) are allowed here.

The GLEP does not make any meantion as to whether it is legal to use
USE dependencies here. I have, however, tested with portage and
portage itself Does The Right Thing when faced with a USE dep in
Display-If-Installed.

>> run: emerge --oneshot $(qlist -IC kde-base/)
>
> Is it guaranteed that your users have portage-utils installed?
> Otherwise the qlist command may not be available.
>

I had thought that we depended on this, but I was mistaken (the
dependency was pulled in via pambase). I guess we could just use
`emerge --update --deep --newuse @world` (and yes, @world is available
in stable portage).

--
Jonathan Callen

* Jonathan Callen schrieb am 19.05.11 um 11:49 Uhr:
> Ulrich Mueller wrote:
>
> >>>>>> On Wed, 18 May 2011, Jonathan Callen wrote:
> >
> >> Display-If-Installed: kde-base/kdelibs[kdeprefix]
> >
> > I don't think that USE dependencies (or any other EAPI specific
> > features) are allowed here.
>
> The GLEP does not make any meantion as to whether it is legal to use
> USE dependencies here. I have, however, tested with portage and
> portage itself Does The Right Thing when faced with a USE dep in
> Display-If-Installed.
>
> >> run: emerge --oneshot $(qlist -IC kde-base/)
> >
> > Is it guaranteed that your users have portage-utils installed?
> > Otherwise the qlist command may not be available.
> >
>
> I had thought that we depended on this, but I was mistaken (the
> dependency was pulled in via pambase). I guess we could just use
> `emerge --update --deep --newuse @world` (and yes, @world is available
> in stable portage).

test -x /usr/bin/qlist && emerge --oneshot $(qlist -IC kde-base/)
|| emerge --update --deep --newuse @world

?

-Marc
--
8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134

On Thu, May 19, 2011 at 2:49 AM, Jonathan Callen <abcd@gentoo.org> wrote:
> Ulrich Mueller wrote:
>
>>>>>>> On Wed, 18 May 2011, Jonathan Callen wrote:
>>
>>> Display-If-Installed: kde-base/kdelibs[kdeprefix]
>>
>> I don't think that USE dependencies (or any other EAPI specific
>> features) are allowed here.
>
> The GLEP does not make any meantion as to whether it is legal to use
> USE dependencies here. *I have, however, tested with portage and
> portage itself Does The Right Thing when faced with a USE dep in
> Display-If-Installed.

reading the code for the version of portage I have installed:

The NewsManager will call Isvalid on each news item and each news item
will scan its restrictions for 'valid-ness' and report that upward. So
if we are lucky, on old versions of portage, portage.isvalidatom will
report the USE-dep as an invalid atom and portage will print mean
errors messages about 'invalid news items' but will not throw up (in
theory).

>
>>> run: emerge --oneshot $(qlist -IC kde-base/)
>>
>> Is it guaranteed that your users have portage-utils installed?
>> Otherwise the qlist command may not be available.
>>
>
> I had thought that we depended on this, but I was mistaken (the
> dependency was pulled in via pambase). *I guess we could just use
> `emerge --update --deep --newuse @world` (and yes, @world is available
> in stable portage).
>
> --
> Jonathan Callen
>
>

Here's the updated news item, which I will be committing very shortly.
Please note that there is absolutely no version of portage that was not in
package.mask that would have problems with an EAPI-2 atom in a news item
because EAPI-2 support was added to portage at the same time as news item
support (they both appeared in portage 2.1.6).

--
Jonathan CallenTitle: Removal of kdeprefix support
Author: Jonathan Callen <abcd@gentoo.org>
Content-Type: text/plain
Posted: 2011-05-22
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: kde-base/kdelibs[kdeprefix]

On 2011-06-06, kdeprefix support will be removed from all KDE ebuilds in
portage. After this is done, only one version of KDE SC will be able to
be installed at a time on a system. If you are currently using
USE=kdeprefix to install multiple versions of KDE SC simultaneously, you
will need to migrate to a non-kdeprefix installation.

To migrate, you will need to set USE=-kdeprefix (or remove the manual
unmasking of that flag in /etc/portage/profile) and rebuild all of the
installed packages in kde-base/. To reinstall these packages, you can
run: emerge --update --deep --newuse @world

On Sun, 22 May 2011 16:52:55 -0400
Jonathan Callen <abcd@gentoo.org> wrote:
> Here's the updated news item, which I will be committing very
> shortly. Please note that there is absolutely no version of portage
> that was not in package.mask that would have problems with an EAPI-2
> atom in a news item because EAPI-2 support was added to portage at
> the same time as news item support (they both appeared in portage
> 2.1.6).

Please don't. This needs to be figured out properly.

--
Ciaran McCreesh