SCIENTIFIC-LINUX-USERS Archives

March 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jon Peatfield <[log in to unmask]>
Reply To:
Jon Peatfield <[log in to unmask]>
Date:
Sat, 5 Mar 2011 01:06:36 +0000
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (31 lines)
On Fri, 4 Mar 2011, Maciej Puzio wrote:

> Files /etc/yum.repos.d/atrpms.repo, atrpms-testing.repo and
> atrpms-bleeding.repo from package atrpms-repo-6-4.el6.x86_64 contain wrong
> baseurls:
> baseurl=http://dl.atrpms.net/el$releasever-$basearch/atrpms/stable
> baseurl=http://dl.atrpms.net/el$releasever-$basearch/atrpms/testing
> baseurl=http://dl.atrpms.net/el$releasever-$basearch/atrpms/bleeding
> Variable $releasever expands to "6.0", while atrpms keeps packages in
> directories el6-i386 and el6-x86_64 - that is, without ".0". As a result,
...

I've never understood why yum doesn't provide a $majorreleasever variable 
as well as $releasever - for those repos where you want to have a single 
tree for each major release (but not for the point releases) and don't 
expect people to edit the .repo files.

I *think* it would be an easy change to yum's config.py (where 
yumvars['releasever'] gets set).  Perhaps it would be better to have a 
syntax in the .conf files to allow variables/values to be defined which 
will be expanded in .repo files (you can already use YUM0-YUM9 environment 
variables but those are horrid names).

Not that I'm expecting any of this to be done by the sl team - they work 
hard enough as-it-is...

Next time I get a chance I'll test it and try to submit a patch to the yum 
maintainers.

  -- Jon

ATOM RSS1 RSS2