From: John Darrington <john@darrington.wattle.id.au>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Symlinks to generic names
Date: Sun, 2 Feb 2014 18:47:07 +0100 [thread overview]
Message-ID: <20140202174706.GA5481@intra> (raw)
In-Reply-To: <20140202164201.GA13629@debian>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
On Sun, Feb 02, 2014 at 05:42:01PM +0100, Andreas Enge wrote:
On Sun, Feb 02, 2014 at 02:40:39PM +0100, John Darrington wrote:
> python3 -> python
For python, the binary python is provided by python-2.7.6. The binary
python3 (and python3.3) is provided by python-3.3.3. And there is
python-wrapper, which installs python-3.3.3 and creates symlinks
python -> python3 etc..
So for python, there is nothing to do - if you need python3, you already
have it.
It seems that whilst guix's python2 package installs a link from python2 -> python
this does not happen for python3.
Generally, we intend to be closer to upstream than debian, for instance;
also to keep maintenance low. So I would be very cautious about adding
symbolic links.
Minimising downstream modifications is certainly a noble goal. The thing
is if we refuse to (say) link lex to flex, then every package which calls "lex"
has to be modified, thus defeating that goal.
Obviously the best option would be to get upstream to adopt our patches. Do
we have any programme to actually make them aware or our patches?
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-02 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 8:21 Symlinks to generic names John Darrington
2014-02-01 18:28 ` Nikita Karetnikov
2014-02-02 0:32 ` Mark H Weaver
2014-02-02 7:34 ` Ludovic Courtès
2014-02-02 7:46 ` John Darrington
2014-02-02 18:06 ` Ludovic Courtès
2014-02-02 13:40 ` John Darrington
2014-02-02 16:42 ` Andreas Enge
2014-02-02 17:47 ` John Darrington [this message]
2014-02-03 13:46 ` Ludovic Courtès
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=20140202174706.GA5481@intra \
--to=john@darrington.wattle.id.au \
--cc=andreas@enge.fr \
--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).