* [devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)]
@ 2000-11-13 0:23 Dmitry V. Levin
2000-11-13 5:40 ` Mikhail Zabaluev
0 siblings, 1 reply; 2+ messages in thread
From: Dmitry V. Levin @ 2000-11-13 0:23 UTC (permalink / raw)
To: devel
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)]
2000-11-13 0:23 [devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)] Dmitry V. Levin
@ 2000-11-13 5:40 ` Mikhail Zabaluev
0 siblings, 0 replies; 2+ messages in thread
From: Mikhail Zabaluev @ 2000-11-13 5:40 UTC (permalink / raw)
To: devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-11-13 5:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-11-13 0:23 [devel] [vdanen@mandrakesoft.com: Re: [Cooker] New update revision scheme? (was: Re: [Announce] MDKA-2000:013 - MandrakeUpdate update)] Dmitry V. Levin
2000-11-13 5:40 ` Mikhail Zabaluev
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git