From: Ricardo Wurmus <rekado@elephly.net>
To: Philippe Veber <philippe.veber@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: List available versions of package.
Date: Wed, 26 Jun 2019 22:25:12 +0200 [thread overview]
Message-ID: <87zhm4w0uv.fsf@elephly.net> (raw)
In-Reply-To: <CAOOOohQv0V7=1V7Ao+0q2h2DfQFo=1Cqo-1uPve9oOawJXE4xQ@mail.gmail.com>
Philippe Veber <philippe.veber@gmail.com> writes:
> I suppose dependencies of these
> packages have to be maintained in the same channel right? Otherwise, if I
> rely on packages from guix distribution, they can be dropped or updated to
> an incompatible version at any moment. That scares me a little, because it
> could break my channel anytime, or am I mistaken?
This is correct; it’s the Linux model of API stability: you need to make
sure that your code remains compatible.
--
Ricardo
next prev parent reply other threads:[~2019-06-26 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 18:27 List available versions of package Philippe Veber
2019-06-10 21:31 ` Tobias Geerinckx-Rice
2019-06-11 7:43 ` Philippe Veber
2019-06-22 11:26 ` Philippe Veber
2019-06-22 19:08 ` Tobias Geerinckx-Rice
2019-06-26 18:32 ` Philippe Veber
2019-06-22 22:46 ` Ricardo Wurmus
2019-06-26 18:43 ` Philippe Veber
2019-06-26 20:25 ` Ricardo Wurmus [this message]
2019-06-30 11:50 ` Philippe Veber
2019-07-02 15:48 ` Leo Famulari
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=87zhm4w0uv.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=philippe.veber@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.
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).