unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] distro: automake: Update to 1.12.6
Date: Fri, 11 Jan 2013 18:19:35 +0100	[thread overview]
Message-ID: <874nin3ae0.fsf@gnu.org> (raw)
In-Reply-To: <87hamnekw5.fsf@karetnikov.org> (Nikita Karetnikov's message of "Fri, 11 Jan 2013 11:37:13 -0500")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>> For Automake, I don’t think it makes sense, though.  Or did you have
>> anything special in mind?
>
> Dependencies.  For instance, you're updating Foo that requires Bar.
> (There is Bar-41 in the repo, but this version of Foo requires 42.
> Also, Bar-42 has some backward incompatible changes.)  If you update Bar
> to 42, it will break other packages.  I suggest to keep three versions:
> the latest version, second-to-last, and third-to-last.

I don’t understand what you mean.  There can be as many different
versions of Automake as you want in the user’s store, and they will
happily coexist.

But that doesn’t mean that the distro itself should keep providing
several versions.  This is a completely orthogonal question.

Or did I misunderstand something?

Ludo’.

  reply	other threads:[~2013-01-11 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22  8:56 [PATCH] distro: automake: Update to 1.12.6 Andreas Enge
2012-12-30 16:24 ` Ludovic Courtès
2012-12-30 16:44   ` Nikita Karetnikov
2012-12-30 18:01     ` Ludovic Courtès
2013-01-11 16:36       ` Nikita Karetnikov
2013-01-11 17:19         ` Ludovic Courtès [this message]
2013-01-03 13:18   ` Andreas Enge
2013-01-03 14:44     ` Ludovic Courtès
2013-01-03 15:24       ` Andreas Enge
2013-01-03 16:04         ` Ludovic Courtès
2013-01-03 16:41           ` Andreas Enge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874nin3ae0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).