[Yum-devel] Patch for yum-versionlock.1 man page

[James Antill]

On Mon, 2009-12-28 at 21:53 +0000, Gerhardus Geldenhuis wrote:
> On Mon, Dec 28, 2009 at 7:31 PM, James Antill <james at fedoraproject.org> wrote:
> >  In future if you could do:
> >
> > git commit -a
> >
> > ...then put the "what's changed" message in the commit, it's easier to
> > merge.
> 
> Will do, do I need to do this as a specific user and would the user
> that does commit need write access or does it go to a "to be approved"
> queue? Apologies for simplistic questions but my versioning experience
> is somewhat limited (shocking I know).

 You have write access to your git instance, you can then use either
"git show" or "git format-patch" to send patches to the list.

>  Maybe I should start a how to
> contribute FAQ.

 That'd be awesome.

> I forgot to clarify something...
> The man page for the versionlock plugin states:
> 
> The  default  place to put package version lock information (one
> package and version per. line)
> 
> reading it implies that you can have multiple entries for a single
> package with different versions...  does it need clarification or can
> you indeed have multiple versions of the same package in the lock
> list. If so I do not understand the "use case" and would like to
> clarify it further in the documentation or remove ambiguity. Would
> greatly appreciate any clarifications.

 Yes, you can "lock" to multiple versions.
 This only seems weird if you think about "versionlock" as locking the
package in the rpmdb from changing ... which is a natural assumption,
and often how the plugin is used, but not quiet what it does. The plugin
actually "locks" the versions of a package yum can see from it's
repositories.

-- 
James Antill - james at fedoraproject.org
http://yum.baseurl.org/wiki/releases
http://yum.baseurl.org/wiki/whatsnew/3.2.26
http://yum.baseurl.org/wiki/YumMultipleMachineCaching