How would the system know what version to downgrade to ? Consider the
case where you've done multiple updates of a particular package along
the way and you want to go to some intermediate step, or where multiple
old versions exist in the repo(s) you have enabled.
How would the system know where
Been thinking about allowdowngrade.
How does that work for things like this:
yum --allowdowngrade update \*
Does that revert you back to GA of your distro?
If we bit the bullet and put in a downgrade command or implemented it in
plugin what is the behavior for it?
I'm not looking for bikeshedd
On Fri, 2008-10-24 at 17:11 -0400, seth vidal wrote:
> On Fri, 2008-10-24 at 17:10 -0400, James Antill wrote:
> > On Fri, 2008-10-24 at 16:52 -0400, seth vidal wrote:
> > > and probably preconf.arch, preconf.releasever, etc, as we move forward,
> > > right?
> >
> > Oh, sure ... and/or just allow
On Fri, 2008-10-24 at 17:10 -0400, James Antill wrote:
> On Fri, 2008-10-24 at 16:52 -0400, seth vidal wrote:
> > On Fri, 2008-10-24 at 15:36 -0400, James Antill wrote:
> > > On Fri, 2008-10-24 at 15:13 -0400, seth vidal wrote:
> > > > Would it make more sense to allow ANY config attribute to be se
On Fri, 2008-10-24 at 16:52 -0400, seth vidal wrote:
> On Fri, 2008-10-24 at 15:36 -0400, James Antill wrote:
> > On Fri, 2008-10-24 at 15:13 -0400, seth vidal wrote:
> > > Would it make more sense to allow ANY config attribute to be set rather
> > > than specifying them? I know it would be tricky
On Fri, 2008-10-24 at 15:36 -0400, James Antill wrote:
> On Fri, 2008-10-24 at 15:13 -0400, seth vidal wrote:
> > Would it make more sense to allow ANY config attribute to be set rather
> > than specifying them? I know it would be tricky to ensure but it would
> > mean not having to constantly add
On Fri, 2008-10-24 at 15:13 -0400, seth vidal wrote:
> Would it make more sense to allow ANY config attribute to be set rather
> than specifying them? I know it would be tricky to ensure but it would
> mean not having to constantly add them in later when they are wanted for
> some arbitrary setup.
On Fri, 2008-10-24 at 15:06 -0400, James Antill wrote:
> Here's a patch Seth and I talked about for how we can easily get rid of
> doConfigSetup() etc. when we break the API, without having to do lots of
> code changes all over the place at the same time.
>
> The basic idea is that if you want to
Here's a patch Seth and I talked about for how we can easily get rid of
doConfigSetup() etc. when we break the API, without having to do lots of
code changes all over the place at the same time.
The basic idea is that if you want to run yum without plugins, instead
of calling:
yb.doConfigSetup
On Fri, 2008-10-24 at 08:45 -0400, James Antill wrote:
> On Fri, 2008-10-24 at 07:46 +0200, Tim Lauridsen wrote:
> > seth vidal wrote:
> > > I think we'll need to preserve compat with older repos for quite a
> > > while.
> > >
> > Yes, we can add the new stuff, but we must be able to work with
On Fri, 2008-10-24 at 07:46 +0200, Tim Lauridsen wrote:
> seth vidal wrote:
> > I think we'll need to preserve compat with older repos for quite a
> > while.
> >
> Yes, we can add the new stuff, but we must be able to work with repos
> missing this extra metadata.
> both in yum and in yum-utils
11 matches
Mail list logo
