[Yum-devel] Pylint errors

[Dennis Gilmore]

On Friday 30 April 2010 02:13:29 pm Seth Vidal wrote:
> On Fri, 30 Apr 2010, Mike Bonnet wrote:
> > On 04/30/2010 02:40 PM, Seth Vidal wrote:
> >> On Fri, 30 Apr 2010, Mike Bonnet wrote:
> >>>>> I think this fall through is on purpose, but I know who would know.
> >>>>> I'll ask spot or dgilmore.
> >>>> 
> >>>> I asked dgilmore he said:
> >>>> [13:59] <dgilmore> skvidal: there both right
> >>>> [13:59] <tibbs> Hmm, OK.
> >>>> [13:59] <skvidal> dgilmore: seriously?
> >>>> [14:00] <dgilmore> skvidal: yep
> >>>> [14:00] <skvidal> ooooooookie doke
> >>>> [14:00] <dgilmore> skvidal: sparcv9 -> sparcv9v ->sparc64 ->sparc64v
> >>>> [14:00] <dgilmore> skvidal: sparcv9 -> sparc64
> >>>> [14:00] <dgilmore> depending on the hardware
> >>>> 
> >>>> so - leave them as is - so we can properly traverse them.
> >>> 
> >>> Isn't the second entry just going to overwrite the first?
> >>> 
> >>>>>> test = {"sparc64v": "sparc64", "sparc64v": "sparcv9v"}
> >>>>>> test
> >>> 
> >>> {'sparc64v': 'sparcv9v'}
> >>> 
> >>> Looks like you need to pick one.
> >> 
> >> do you have a preference? :)
> > 
> > If the dict is trying to create a "most powerful/modern to least
> > powerful/modern" ordering, I'd suggest this:
> > 
> > # sparc
> > "sparc64v": "sparc64",
> > "sparc64": "sparcv9v",
> > "sparcv9v": "sparcv9",
> > "sparcv9": "sparcv8",
> > "sparcv8": "sparc",
> > "sparc": "noarch",
> > 
> > Assuming sparc64 ≥ sparcv9v, which is what the conversation with
> > dgilmore seems to imply.
> 
> Except I don't think you can do sparc64-> sparcv9v
you can't
64 bit builds are  sparc64v and sparc64
32 bit builds are sparcv9v sparcv9 sparcv8 sparc

niagara based hardware is capable of installing sparcv9v and sparc64v
ultrasparc is capable of installing and running sparcv9 and sparc64.   but it 
is not at all capable of running sparcv9v

> I think you can only do sparc64v -> sparcv9v
> 
> but I don't actually KNOW that.

at some point soon this will all be moot.  glibc is learning to dynamically 
optimise so we will only build sparcv9 and sparc64 and optimisation will be at 
run time not build time.  In theory we could build everything optimised for 
niagara but we only do glibc.

Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.baseurl.org/pipermail/yum-devel/attachments/20100430/b299597c/attachment-0001.pgp>