On Fri, Dec 17, 2021 at 12:59:16PM -0500, Leo Famulari wrote:
> Currently we have a problem caused by glibmm-2.64 propagating two
> different versions of libsigc++:
>
> https://issues.guix.gnu.org/52519
>
> I think this is something that is rarely desirable.
>
> Maybe the linter could check for
Currently we have a problem caused by glibmm-2.64 propagating two
different versions of libsigc++:
https://issues.guix.gnu.org/52519
I think this is something that is rarely desirable.
Maybe the linter could check for cases like this? Of course, "cases like
this" still needs to be defined exactl
. I’d package these as pure source bundles, so their
individual dependency information won’t be reflected in Guix, that
will be left to apps.
My question now is how to deal with multiple versions of the same
elm package, e.g “elm/browser”. My own app I’m trying to package
depends on “elm/browser
(x) (if (eq? x #\.) #\_ x)) version)
".tar.bz2"))
(sha256
(base32
"0rs94vdmg34bwwj23fllva6mhrml2i7mvmlb11zyrk1k5818q34i"))
Is this a workable approach? If not, how could I go about adding
multiple versions?
My ot
".tar.bz2"))
> (sha256
>(base32
> "0rs94vdmg34bwwj23fllva6mhrml2i7mvmlb11zyrk1k5818q34i"))
>
>
> Is this a workable approach? If not, how could I go about adding
> multiple versions?
In principle this should be enough, but havi
Dmitry Bogatov skribis:
> Currently, I am at master branch. I want install parallel-20151122.
> But it is gone since 0877e. I propose to keep *all* versions,
> but just 'parallel' refer to latest.
First, I think it’s important to distinguish the source (the package
recipes in gnu/packages/*.scm)
Alex Kost writes:
> Dmitry Bogatov (2015-12-27 19:47 +0300) wrote:
>
>> * Alex Kost [2015-12-27 17:11:20+0300]
>>> Dmitry Bogatov (2015-12-27 02:02 +0300) wrote:
>>>
>>> > * By default, ~/.guix-profile/share/emacs/site-lisp/guix.d is not in
>>> > load-path. `emacs-no-x` exports no variable
* Alex Kost [2015-12-27 17:11:20+0300]
> Dmitry Bogatov (2015-12-27 02:02 +0300) wrote:
>
> > * By default, ~/.guix-profile/share/emacs/site-lisp/guix.d is not in
> > load-path. `emacs-no-x` exports no variables. So, if I install
> > some emacs library, like `emacs-f`, evaluating (requi
> >> 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,
> > co
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/interpre
Dmitry Bogatov writes:
>> 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.ve
* Pjotr Prins [2015-12-27 13:41:52+0100]
> On Sun, Dec 27, 2015 at 12:20:27PM +0300, Dmitry Bogatov wrote:
> > Currently, I am at master branch. I want install parallel-20151122.
> > But it is gone since 0877e. I propose to keep *all* versions,
> > but just 'parallel' refer to latest.
>
> Use a c
Dmitry Bogatov (2015-12-27 02:02 +0300) wrote:
> * By default, ~/.guix-profile/share/emacs/site-lisp/guix.d is not in
> load-path. `emacs-no-x` exports no variables. So, if I install
> some emacs library, like `emacs-f`, evaluating (require 'f) in emacs
> fails. It is... unexpected.
On Sun, Dec 27, 2015 at 12:20:27PM +0300, Dmitry Bogatov wrote:
> Currently, I am at master branch. I want install parallel-20151122.
> But it is gone since 0877e. I propose to keep *all* versions,
> but just 'parallel' refer to latest.
Use a combination of git hash values (to generate the version
Dmitry Bogatov writes:
>> Then there is the combinatorial explosion. If you have 20 libraries in
>> 10 versions each that are needed to build a derived binary, then there
>> will be 10^20 possible combinations. Which of them would you like to
>> support?
>
> Build binaries with latest versions o
* Andreas Enge [2015-12-27 10:48:32+0100]
> On Sun, Dec 27, 2015 at 12:20:27PM +0300, Dmitry Bogatov wrote:
> > Currently, I am at master branch. I want install parallel-20151122.
> > But it is gone since 0877e. I propose to keep *all* versions,
> > but just 'parallel' refer to latest.
>
> This w
On Sun, Dec 27, 2015 at 12:20:27PM +0300, Dmitry Bogatov wrote:
> Currently, I am at master branch. I want install parallel-20151122.
> But it is gone since 0877e. I propose to keep *all* versions,
> but just 'parallel' refer to latest.
This would be a nightmare to maintain. And what do you do abo
> > In my attempt to understand Guix, get used to it and use
> > it's advantages, I got following considerations that I would like
> > to discuss with more experienced users:
> >
> > * Guix provides first-class support for multiple versions of packages.
>
Guix provides first-class support for multiple versions of packages.
> By first class I mean, that you don't need to do anything special
> to get this support, unlike Gentoo, which for example, supports
> multiple versions of Python and Ruby, but not Guile or GHC.
>
>
Hello!
In my attempt to understand Guix, get used to it and use
it's advantages, I got following considerations that I would like
to discuss with more experienced users:
* Guix provides first-class support for multiple versions of packages.
By first class I mean, that you don't
Andreas Enge skribis:
> On Sat, Dec 07, 2013 at 12:13:57PM +0100, John Darrington wrote:
>> Can we have Texinfo 5 and Texinfo 4 concurrently in guix?
>
> Yes, without problem. You may add a variable texinfo-4; with a bit of
> luck, it can simply inherit from texinfo with a few added modifications
On Sat, Dec 07, 2013 at 12:13:57PM +0100, John Darrington wrote:
> Can we have Texinfo 5 and Texinfo 4 concurrently in guix?
Yes, without problem. You may add a variable texinfo-4; with a bit of
luck, it can simply inherit from texinfo with a few added modifications.
You may have a look at Qt 4 an
I'm trying to package Octave.
It seems that it needs Texinfo to build. Furthermore, it does not work with
Texinfo 5.2 which
is what we have in guix. I looked at patching it, but it would be non-trivial.
I suspect there is still quite a bit of software in the wild that does not work
with Texi
23 matches
Mail list logo
