unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Different versions of a package in the same profile?
Date: Mon, 03 Nov 2014 09:58:50 +0100	[thread overview]
Message-ID: <874mugu0c5.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPNsAKhtiK29pb4T02_2mssrULTc6u27qKRddTUr5hsgsw@mail.gmail.com> (Federico Beffa's message of "Sun, 2 Nov 2014 19:52:44 +0100")

Federico Beffa <beffa@ieee.org> skribis:

> Andreas Enge <andreas@enge.fr> writes:
>
>> On Sun, Nov 02, 2014 at 06:22:28PM +0100, Ludovic Courtès wrote:
>> There is also the question of conflicts with identical file names. They are
>> already there now, but their probability should be higher with identical
>> package names. Maybe we need to rethink the handling of conflicts also.
>
> In the past I did use the packaging system called SEPP
>
> http://oss.oetiker.ch/op-sepp/

Interesting.

> It allow installing several versions of a program on a single system.
> The way they use to avoid naming conflicts it to systematically add a
> suffix to binary names, with the suffix corresponding to the version of
> the package.  They even went one step further and they added a suffix
> with the initials of the administrator who packaged the application.
>
> Each program was available with several names. For program foo:
> - foo
> - foo-1.2.3
> - foo-1.2.3-fb
> Obviously if more foo versions were installed, only one would be
> referred to by foo.  The others were available with versioned names.
>
> As a user, the system did work very well.
>
> To handle updating, specifying foo should update the version owning
> the name foo.

OK, this is a strategy similar to what Andreas was suggesting.

> To update another version one would give the versioned name
> "foo-1.2.3".

I see.

Ludo’.

  reply	other threads:[~2014-11-03  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02 18:52 Different versions of a package in the same profile? Federico Beffa
2014-11-03  8:58 ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-27 12:24 Problems with downloading from https Ludovic Courtès
2014-10-27 13:27 ` Alex Kost
2014-10-27 14:43   ` Mark H Weaver
2014-10-27 16:24     ` Ludovic Courtès
2014-10-27 16:44       ` Alex Kost
2014-10-28  8:03         ` Ludovic Courtès
2014-10-29 22:22           ` Andreas Enge
2014-10-30  7:27             ` Alex Kost
2014-10-30  7:49               ` Andreas Enge
2014-10-30 12:31                 ` Alex Kost
2014-10-30 12:38                   ` Andreas Enge
2014-10-30 23:07                     ` Different versions of a package in the same profile? Ludovic Courtès
2014-11-01 10:46                       ` Andreas Enge
2014-11-02 17:22                         ` Ludovic Courtès
2014-11-02 17:39                           ` 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=874mugu0c5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.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).