Andy Wingo skribis:
> On Fri 14 Apr 2017 14:54, l...@gnu.org (Ludovic Courtès) writes:
>
>>> I think we should make it so that the lower-potluck-package process
>>> prefers "core" packages if available, and only goes to the channel if
>>> the core does not provide a package matching the specifica
On Fri 14 Apr 2017 14:54, l...@gnu.org (Ludovic Courtès) writes:
>> I think we should make it so that the lower-potluck-package process
>> prefers "core" packages if available, and only goes to the channel if
>> the core does not provide a package matching the specification.
>>
>> I think this is
Hi!
Andy Wingo skribis:
> On Thu 13 Apr 2017 17:42, l...@gnu.org (Ludovic Courtès) writes:
[...]
>>> (The wip-potluck branch extends guix build -f to recognize potluck
>>> packages.)
>>
>> Oh I see, I was wondering why that was working. :-)
>>
>> Maybe we could have ‘guix potluck build’ or so
Hi :)
On Thu 13 Apr 2017 17:42, l...@gnu.org (Ludovic Courtès) writes:
> Turns out Guile-Present is already in Guix proper, but Guile-JPEG isn’t!
> :-)
Oh neat :)
>> (The wip-potluck branch extends guix build -f to recognize potluck
>> packages.)
>
> Oh I see, I was wondering why that was worki
Hi!
Andy Wingo skribis:
> This is an update on "guix potluck", an attempt to support a more
> decentralized way of developing Guix packages, as a complement to the
> main package set.
>
> I have a number of packages that I never packaged for external use, at
> least beyond putting them in a git
Hi!
This is an update on "guix potluck", an attempt to support a more
decentralized way of developing Guix packages, as a complement to the
main package set.
I have a number of packages that I never packaged for external use, at
least beyond putting them in a git repo somewhere. Here's an exampl
