From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Dmitry Bogatov <KAction@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Multiple versions
Date: Sun, 27 Dec 2015 16:58:17 +0100 [thread overview]
Message-ID: <20151227155817.GA1862@thebird.nl> (raw)
In-Reply-To: <20151227144002.GA23049@sagulo>
On Sun, Dec 27, 2015 at 05:40:02PM +0300, Dmitry Bogatov wrote:
> It makes sence. The only problem is find required hash. Is it any idea
> to automate it?
Not really.
> > > In case of haskell/python/ruby libraries, I propose keep all versions
> > > multiplied by every version of compiler/interpreter.
> >
> > I do the same with Ruby using profiles. I have any number of interpreters
> > installed for testing and any number of libraries using either guix or
> > the lib path with a profile in there.
>
> But how do you solve problem, that for example you want library foo-999.very.new,
> compiled with ruby-1.8, but they never existed at same time in guix
> package tree?
You can use source trees with GUIX_PACKAGE_PATH. Maybe you'll have to
move them to a source file. It is less hard than it looks if you are
committed to the idea.
Pj.
next prev parent reply other threads:[~2015-12-27 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 23:02 Multiple versions Dmitry Bogatov
2015-12-27 5:26 ` Pjotr Prins
2015-12-27 9:20 ` Dmitry Bogatov
2015-12-27 9:48 ` Andreas Enge
2015-12-27 10:41 ` Dmitry Bogatov
2015-12-27 12:28 ` Ricardo Wurmus
2015-12-27 12:41 ` Pjotr Prins
2015-12-27 14:40 ` Dmitry Bogatov
2015-12-27 15:41 ` Ricardo Wurmus
2015-12-27 16:41 ` Dmitry Bogatov
2015-12-27 15:58 ` Pjotr Prins [this message]
2015-12-29 15:21 ` Ludovic Courtès
2015-12-27 14:11 ` Alex Kost
2015-12-27 16:47 ` Emacs load path (was: Re: Multiple versions) Dmitry Bogatov
2015-12-27 21:42 ` Emacs load path Alex Kost
-- strict thread matches above, loose matches on Subject: below --
2016-07-16 13:57 multiple versions Vincent Legoll
2016-07-16 20:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151227155817.GA1862@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=KAction@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.