On Thu, May 10, 2012 at 01:10:48PM -0400, Jim Ramsay wrote:
> On Thu, Apr 26, 2012 at 05:06:45PM -0300, Alexis Ballier wrote:
> > wouldnt adding a sse2 useflag and putting it in REQUIRED_USE solve the
> > problem ?
> >
> > afaik portage wont even try to upgrade if people have -sse2
>
> This is an interesting idea, as it could automatically downgrade users to
> 10.3 without requiring any masking. I like that.
Hmmm... After some testing, I don't think this is how it works.
It looks to me like if I try to do an upgrade on a system that has
USE=-sse2, it doesn't downgrade automatically. Nor does it simply skip
the upgrade. At least with portage 2.1.10.57, I get the following fatal
output:
-------
# USE=-sse2 emerge -uDN world -p
...
!!! Problem resolving dependencies for www-plugins/adobe-flash from
@selected ... done!
!!! The ebuild selected to satisfy "www-plugins/adobe-flash" has unmet
requirements.
- www-plugins/adobe-flash-11.2.202.235::local USE="64bit (multilib)
-32bit -kde -sse2 -vdpau"
The following REQUIRED_USE flag constraints are unsatisfied:
sse2
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
-------
So in light of this, I think I'm going to keep the fatal pkg_pretend
with /proc/cpuinfo check in the 11.2 ebuild, since that's the only way I
can do the check in a way that meets my 3 requirements:
-> No annoyance for users who have sse2 instructions present
-> runs at install time in a non-ignorable (fatal) way
-> provides useful downgrade instructions to the user
Too bad pkg_pretend doesn't fire during 'emerge -p' -> That would be
even better.
Any other suggestions on how I can make this work better?
--
Jim Ramsay
