[gentoo-dev] Heads up: libjpeg-turbo stabilization, becoming the default

[gentoo-dev] Heads up: libjpeg-turbo stabilization, becoming the default

[Samuli Suominen]

libjpeg-turbo stabilization is happening for amd64/x86 at
http://bugs.gentoo.org/360715

- the gentoo-x86 has been converted to virtual/jpeg to support this.
- we have no bugs reported against the package.
- libjpeg-turbo is default in virtual/jpeg

so just heads up.

[gentoo-dev] Virtual default changes for old users, was: Heads up: libjpeg-turbo stabilization, becoming the default

[Christopher Head]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 27 Mar 2011 11:33:03 +0300
Samuli Suominen <ssuominen@gentoo.org> wrote:

> libjpeg-turbo stabilization is happening for amd64/x86 at
> http://bugs.gentoo.org/360715
> 
> - the gentoo-x86 has been converted to virtual/jpeg to support this.
> - we have no bugs reported against the package.
> - libjpeg-turbo is default in virtual/jpeg
> 
> so just heads up.
> 

Hi everyone,

Just a user, not a developer, but:

The third point of this message made me wonder about something. New
installs will get libjpeg-turbo, as it's the default. Old users may
never know it exists! It seems that making lbjpeg-turbo the default
implementation of virtual/jpeg is expressing some small preference in
favour of it, but old users will never be presented with the choice to
switch. It seems like this is a bit of a gap in package management,
that even if a "better" package becomes available and becomes the
default implementation of a virtual, existing users will keep using the
"worse" package for no other reason than that it's already installed
(and there's no message anywhere even telling them that the change
happened).

Does anyone think this is suboptimal and that it might be nice to
investigate alternatives?

Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk3nHIkACgkQXUF6hOTGP7ftqwCgho+EhlOnvy1swE7nOE21TcMq
wiIAn1Vr9fRZmvRIvyO5vsILWT9XzSxi
=GIqk
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Virtual default changes for old users, was: Heads up: libjpeg-turbo stabilization, becoming the default

[Zac Medico]

On 06/01/2011 10:15 PM, Christopher Head wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, 27 Mar 2011 11:33:03 +0300
> Samuli Suominen <ssuominen@gentoo.org> wrote:
> 
>> libjpeg-turbo stabilization is happening for amd64/x86 at
>> http://bugs.gentoo.org/360715
>>
>> - the gentoo-x86 has been converted to virtual/jpeg to support this.
>> - we have no bugs reported against the package.
>> - libjpeg-turbo is default in virtual/jpeg
>>
>> so just heads up.
>>
> 
> Hi everyone,
> 
> Just a user, not a developer, but:
> 
> The third point of this message made me wonder about something. New
> installs will get libjpeg-turbo, as it's the default. Old users may
> never know it exists! It seems that making lbjpeg-turbo the default
> implementation of virtual/jpeg is expressing some small preference in
> favour of it, but old users will never be presented with the choice to
> switch. It seems like this is a bit of a gap in package management,
> that even if a "better" package becomes available and becomes the
> default implementation of a virtual, existing users will keep using the
> "worse" package for no other reason than that it's already installed
> (and there's no message anywhere even telling them that the change
> happened).
> 
> Does anyone think this is suboptimal and that it might be nice to
> investigate alternatives?

A couple of alternatives come to mind:

A) Create a news item to notify people who have media-libs/jpeg
installed that there is an alternative.

B) Put media-libs/jpeg in package.mask, so that migration happens
automatically.
-- 
Thanks,
Zac