From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>, Ryan Prior <ryanprior@hey.com>
Subject: Re: Finding versions of packages
Date: Fri, 18 Dec 2020 16:21:46 +0100 [thread overview]
Message-ID: <87wnxf9m2d.fsf@gnu.org> (raw)
In-Reply-To: <86y2hzmdbb.fsf@gmail.com> (zimoun's message of "Tue, 15 Dec 2020 14:03:20 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Tue, 15 Dec 2020 at 12:16, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> However, doing such composition on a per-package basis and as the
>> default way of composing packages is inefficient and, more importantly,
>> the resulting compositions may not work. A package written for Python 2
>> may not work with Python 3, and so on.
>
> About inefficiency, I agree. The number of inferiors should be
> minimized, IMHO.
>
> By “the resulting composition may not work”, you mean that what is
> propagated may be incompatible, right? For example, bytecode or ABI
> incompatibilities.
Yes, all sort of incompatibilities could arise.
The great thing with having all the package definitions in a single tree
is that we know they were tested to work together well (hopefully). If
you start composing packages taken from different revisions, you lose
that guarantee.
Ludo’.
next prev parent reply other threads:[~2020-12-18 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 22:08 Finding versions of packages (was: [outreachy] Walk through the Git history) Ryan Prior
2020-12-14 10:38 ` Finding versions of packages Ludovic Courtès
2020-12-14 12:41 ` zimoun
2020-12-15 11:16 ` Ludovic Courtès
2020-12-15 13:03 ` zimoun
2020-12-18 15:21 ` Ludovic Courtès [this message]
2020-12-14 12:31 ` Finding versions of packages (was: [outreachy] Walk through the Git history) zimoun
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=87wnxf9m2d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ryanprior@hey.com \
--cc=zimon.toutoune@gmail.com \
/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).