Bug 505410 - RFE: Allow overriding releasever with a specific version in addition to a package
Summary: RFE: Allow overriding releasever with a specific version in addition to a pac...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-11 20:03 UTC by Bruno Wolff III
Modified: 2014-01-21 23:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-17 18:53:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bruno Wolff III 2009-06-11 20:03:29 UTC
Description of problem:
It makes doing a yum update a little bit easier if I can say something like:
yum --releasever=11 update
and not have to manually tweak repo files or alternatively fetching a copy of fedora-release and trying to install that first.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 James Antill 2009-06-11 21:50:00 UTC
 Upstream this is easy to do, in code, now. And also upstream it's possible to have cachedir be releasever specific.
 The biggest problem is getting something from the command line into yum before releasever is used (as a plugin you can't do it atm. because releasever is used before plugin arguments are parsed). In theory we can add it to core, but it seems like a pretty small edge case to add a core option for.

Comment 2 seth vidal 2009-09-17 18:53:00 UTC
I think having cachedir be able to use $releasever/$basearch takes care of this problem.
for example:

cachedir=/var/cache/yum/$basearch/$releasever

I've made this the default in the yum.conf in rawhide/f12.


Note You need to log in before you can comment on or make changes to this bug.