[devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)]

[devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)]

[Dmitry V. Levin]

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

Greetings!

Информация к размышлению (на тему: как мы будем делать?):

----- Forwarded message from Vincent Danen <vdanen@mandrakesoft.com> -----

Date: Fri, 10 Nov 2000 22:47:21 -0700
From: Vincent Danen <vdanen@mandrakesoft.com>
To: cooker@linux-mandrake.com
Subject: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)

On Fri Nov 10, 2000 at 11:15:21PM +0100, Alexander Skwar wrote:

> So sprach Vincent Danen am Fri, Nov 10, 2000 at 03:43:51PM -0700:
> >  This update for MandrakeUpdate allows MandrakeUpdate to install updated
> >  RPMs using the new update revision scheme.  This update is necessary
> 
> New update revision scheme?  What's that?

Updates in MandrakeUpdate will always have a dotted revision number
now (like 1.1mdk) so that new cooker packages will *always* remain
newer.  Due to the differences in spec files, I sometimes end up
building three separate packages for the same thing (ie. bind has
-1.1mdk, -1.2mdk, -1.3mdk).  A -1mdk will appear in cooker (same as
the updates), but if changes are made, the next revision in cooker
would be -2mdk.  If I did it the old-fashioned way with MU, there
would be -1mdk, -2mdk, -3mdk for the same thing meaning that 6.0
update of bind (-3mdk old way) would be higher than a newer bind in
cooker (which could be -2mdk).  This way, updates has -1.3mdk so -2mdk
in cooker will always be higher.

Make sense?  =)

-- 
vdanen@mandrakesoft.com, OpenPGP key available on www.keyserver.net
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD
 - Danen Consulting Services    www.danen.net, www.freezer-burn.org
 - MandrakeSoft, Inc.           www.linux-mandrake.com

Current Linux uptime: 3 days 22 hours 44 minutes.

----- End forwarded message -----


Regards,
	Dmitry

+-------------------------------------------------------------------------+
Dmitry V. Levin     mailto://ldv@fandra.org
Software Engineer   PGP pubkey http://www.fandra.org/users/ldv/pgpkeys.html
IPLabs Linux Team   http://linux.iplabs.ru
Fandra Project      http://www.fandra.org
+-------------------------------------------------------------------------+
UNIX is user friendly. It's just very selective about who it's friends are.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)]

[Mikhail Zabaluev]

Hello Dmitry,

On Mon, Nov 13, 2000 at 03:23 +0300, Dmitry V. Levin wrote:
>
> Greetings!
> 
> Информация к размышлению (на тему: как мы будем делать?):
> 
> ----- Forwarded message from Vincent Danen <vdanen@mandrakesoft.com> -----
> 
> Date: Fri, 10 Nov 2000 22:47:21 -0700
> From: Vincent Danen <vdanen@mandrakesoft.com>
> To: cooker@linux-mandrake.com
> Subject: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)
> 
> On Fri Nov 10, 2000 at 11:15:21PM +0100, Alexander Skwar wrote:
> 
> > So sprach Vincent Danen am Fri, Nov 10, 2000 at 03:43:51PM -0700:
> > >  This update for MandrakeUpdate allows MandrakeUpdate to install updated
> > >  RPMs using the new update revision scheme.  This update is necessary
> > 
> > New update revision scheme?  What's that?
> 
> Updates in MandrakeUpdate will always have a dotted revision number
> now (like 1.1mdk) so that new cooker packages will *always* remain
> newer.  Due to the differences in spec files, I sometimes end up
> building three separate packages for the same thing (ie. bind has
> -1.1mdk, -1.2mdk, -1.3mdk).  A -1mdk will appear in cooker (same as
> the updates), but if changes are made, the next revision in cooker
> would be -2mdk.  If I did it the old-fashioned way with MU, there
> would be -1mdk, -2mdk, -3mdk for the same thing meaning that 6.0
> update of bind (-3mdk old way) would be higher than a newer bind in
> cooker (which could be -2mdk).  This way, updates has -1.3mdk so -2mdk
> in cooker will always be higher.
> 
> Make sense?  =)

Разумно =)

-- 
Stay tuned,
  MhZ                                    mailto:mookid@sigent.ru
-----------
And I heard Jeff exclaim,
As they strolled out of sight,
"Merry Christmas to all --
You take credit cards, right?"
		-- "Outsiders" comic
_______________________________________________
Devel mailing list
Devel@linux.iplabs.ru
http://www.logic.ru/mailman/listinfo/devel