On Fri, 15 Nov 2019 10:07:38 +0100
Pierre Neidhardt wrote:
Hello,
When can I expect our changes to be merged? There's a new Jami version
(20191115.5.b0a579d), I would like to update it to, but a strange
conflict stops me from running "git pull". I also can't investigate the
issue, until webkit-gt
Hi all,
I agree with this:
> The whole point of package management is that you can use module
> building blocks. By having to specify the sub-dependencies in a top
> level definition kinda breaks the whole modular thing.
It is quite frustrating to have to specify transitive dependencies at the t
> It is quite frustrating to have to specify transitive dependencies at
> the top level. I’m not sure what else is to be done, though.
How about having something like "propagated-input" for rust source
dependencies? The top level package could use the source deps as
development-inputs so the
Hello!
Martin Becze skribis:
> Sorry for digging up and old issue, but i just saw commit
> 86e443c71d4d19e6f80cad9ca15b9c3a301c738c
>
>> It makes for a very large package definition, but we
> wouldn't have to ensure thousands of other rust libraries built so we
>
> The whole point of package man
Hi Chris,
Christopher Baines skribis:
> ---
> Makefile.am | 8 +-
> bin/cuirass-send-events.in | 90 +++
> src/cuirass/base.scm| 9 ++-
> src/cuirass/database.scm| 142 +---
> src/cuirass/http.scm| 24
Christopher Baines skribis:
> ---
> src/cuirass/base.scm | 5 +
> src/cuirass/database.scm | 6 +-
> src/cuirass/http.scm | 9 +
> 3 files changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/src/cuirass/base.scm b/src/cuirass/base.scm
> index fd10e35..943a4f2 100644
Hi Chris,
Chris Marusich skribis:
> I've been updating some systems with a fairly old version of Guix, so
> perhaps that contributed to the very long "guix pull" times. It felt
> like Guix wanted to compile the whole world just to run "guix pull".
Could it be that those old systems were talkin
Hi Konrad,
Konrad Hinsen skribis:
> YAML is for kids. Real managers won't settle for less than full XML. ;-)
>
> Seriously, as a power user, I am perfectly happy with Guile for
> everything. I certainly don't want less. And for now, it's safe to
> assume that most Guix users are power users. The
Howdy!
Konrad Hinsen skribis:
>> I think having ephemeral + persistent and declarative + imperative is
>> cool—I’d call that “flexible” rather than “messy”. :-)
>
> I agree. What's messy is how the concepts map to commands. How many Guix
> users understand that profiles are persistent environme
Hi Vagrant,
Vagrant Cascadian skribis:
> On 2019-05-28, Vagrant Cascadian wrote:
>> On 2019-05-16, Vagrant Cascadian wrote:
>>> So in a bit of a focused run of packaging, I've been chasing the
>>> dependency chain necessary to get guix building on Debian:
>
> Summary: all the dependencies are in
Hello!
Pierre Neidhardt skribis:
> Sorry for the troubles, indeed only the big "texlive" package is fully
> functional with Guix at the moment.
Hmm, is this accurate? I mean, all the packages uses ‘texlive-union’
internally, and with the texlive profile hook, we should now be able to
make do w
Ludovic Courtès writes:
> Hi Chris,
>
> Christopher Baines skribis:
>
>> ---
>> Makefile.am | 8 +-
>> bin/cuirass-send-events.in | 90 +++
>> src/cuirass/base.scm| 9 ++-
>> src/cuirass/database.scm| 142 +--
Pierre Neidhardt writes:
> Sorry for the troubles, indeed only the big "texlive" package is fully
> functional with Guix at the moment.
This statement could be misunderstood. The individual texlive packages
work pretty well for many use cases. I myself have been using them
since they have be
Ludovic Courtès writes:
> Christopher Baines skribis:
>
>> ---
>> src/cuirass/base.scm | 5 +
>> src/cuirass/database.scm | 6 +-
>> src/cuirass/http.scm | 9 +
>> 3 files changed, 19 insertions(+), 1 deletion(-)
>>
>> diff --git a/src/cuirass/base.scm b/src/cuirass/bas
Hi,
Marius Bakke writes:
> I've read some of the changes and they LGTM. If Cuirass is happy, I
> think you can go ahead and merge the branch. \o/
I just put everything together and rebased it all on master, fixing
several typos as I did so. :) It seems that “ghc@8.6.5” has changed a
few day
Hello Guix!
So I was able to successfully package 'gnome-characters'. The following
is the package definition. I have attacted the package definition
(gnome-characters.scm) with this email.
This is the first time for me with packaging. Can anyone help me how to
move forward from here, to integrat
On Sat, 16 Nov 2019 19:50:12 -0500 Raghav Gururajan
wrote
> Hello Guix!
>
> So I was able to successfully package 'gnome-characters'. The following
> is the package definition. I have attacted the package definition
> (gnome-characters.scm) with this email.
>
> This is t
> What I would have liked is to somehow replace the #:cargo-inputs
> argument (which is build-system-specific and thus “opaque”) with regular
> ‘native-inputs’ or ‘inputs’ field.
That would be lovely! I always wondered why "#:cargo-inputs" existed.
On Sat, Nov 16, 2019 at 10:33:32PM +0100, Ludovic Courtès wrote:
> Hello!
>
> Martin Becze skribis:
>
> > Sorry for digging up and old issue, but i just saw commit
> > 86e443c71d4d19e6f80cad9ca15b9c3a301c738c
> >
> >> It makes for a very large package definition, but we
> > wouldn't have to ensu
20 matches
Mail list logo
