[Yum] error report -- latest tarball yum-20030203.tar.gz
dawson at fnal.gov
Tue Feb 4 14:09:58 UTC 2003
I think it's a good idea. At some point you just have to diverge and go for
the python2 and rpm 4.2. But I have one comment.
When you do the breakoff, can you make it everything greater than 2.0 instead
of 1.0. That way, at some point, you can actually have a 1.0 release for the
python 1.x. rpm 4.0x.
I know that sounds trivial, but some people simply don't think a product is
usable until it hit's it's 1.0 release. It's a mental thing I know, but it's
in alot of people's minds that way.
You could also say then that the yum 1.0 goes with python 1, and yum 2.x goes
with python 2.
seth vidal wrote:
>>Of course the build host cannot know, or infer where its
>>product will later be installed.
>>Probably the best one could do is query rpm version at
>>runtime, and then if == 4.1.x, set a flag, and if it faults
>>out, catch and return a error message in the python code
>>suggesting this as a possible issue.
> ok I know another answer.
> an easier one - but it might not be easier for the people who have to
> implement it.
> I'd like some feedback on this.
> Systems that can and are using rpm 4.0.4 and/or the rpm404 bindings
> should use yum < 1.0.
> Those people using rpm 4.2 or higher should use yum > 1.0
> My goals were/are mostly to follow the red hat releases. 7.1, 7.2, 7.3
> and 8.0 are all served by yum <1.0 (0.9.4 in this case)
> TNV (8.1 or something I'd guess) will use yum > 1.0.
> Keeping compatibility for all versions of rpm forever will make the code
> a mess, but not keeping some compatibility makes it harder for users.
> The things I intend to put into yum include comps.xml support and an
> array of other things that will REQUIRE python2.x and a lot of modules
> built for python2.x
> I've been following anaconda fairly loosely - in rhl 8.0 anaconda did
> an: import rpm404 as rpm.
> in the current beta anaconda has been ported to work with rpm 4.2, so I
> did the same.
> What do people think about that? Is that a horrible idea? Or just lazy?
> Maybe this is the time for the break b/c of how much of a departure rpm
> is at this point.
> The new requirements for later versions of yum would be:
> rpm-python >= 4.2
> python >= 2.X
> is that not fun for a lot of people?
> Yum mailing list
> Yum at lists.dulug.duke.edu
Troy Dawson dawson at fnal.gov (630)840-6468
Fermilab ComputingDivision/OSS CSI Group
More information about the Yum