[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: guix environment ad-hoc manifests
From: |
Zelphir Kaltstahl |
Subject: |
Re: guix environment ad-hoc manifests |
Date: |
Thu, 22 Oct 2020 22:05:10 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
On 10/22/20 6:00 PM, help-guix-request@gnu.org wrote:
> Reza Alizadeh Majd <r.majd@pantherx.org> writes:
>
>> On Thu, 22 Oct 2020 13:53:10 +0200
>> Ricardo Wurmus <rekado@elephly.net> wrote:
>>
>>> Reza Alizadeh Majd <r.majd@pantherx.org> writes:
>>>
>>>> it would also be great to be able to pass list of ad-hoc packages,
>>>> using a manifest file, something like --ad-hoc-manifest switch. or
>>>> maybe there is such option already available that I missed.
>>> What would that look like? Just a file containing package names?
>>>
>> yes, a possible use-case would be to provide a development
>> environment for a software which is not packaged yet. during
>> development phase, we could easily update this manifest file and
>> include third-parties we need to use.
> But isn’t this exactly what you can use a manifest file for already?
> “guix environment” not only accepts a file that describes a package, but
> also a manifest.
Or perhaps a solution could be to simply allow multiple --manifest
files, so that one could oneself distinguish between them via file name,
but Guix uses them as if their content was merged in one file instead?
- Re: guix environment ad-hoc manifests,
Zelphir Kaltstahl <=