question on setting up guix.scm for project development

question on setting up guix.scm for project development

[Andy Tai]

Hi, guix allows setting up an environment containing all the
dependencies for development of a package; this can be done via a
guix.scm file containing the package definition.

My question is, if I am developing a package which has dependencies
with newer versions than what is available in the guix repo, how can I
use the guix.scm file to bring in the new version of the dependencies?
 As an example:

Say  my package "my-package" has dependencies d1, d2, d3
where d2 in the current guix package repo is at version 0.1.2 but I
need a later release version 0.1.4; so I tried something like this:

----guix.scm---
(use-modules (guix packages)
   ....)

(define-public d2-0.1.4
   (package
       (name "d2")
       (version "0.1.4")

   ...
)


(define-public my-package
   (package
      (name "my-package")
      (version "0.1")
     ...


     (input (list d1 d2-0.1.4 d3...)
    ....
))

my-package

---end guix.scm--


and if I use

guix shell -f -d ./guix.scm

this does not seem to generate an environment that contains the new
dependency, that is d2 version 0.1.4

I wonder how can this made to work?  Ideally no need to create a
private channel or such..  Thanks for info on this.

Fwd: question on setting up guix.scm for project development

[Andy Tai]

Hi, guix allows setting up an environment containing all the
dependencies for development of a package; this can be done via a
guix.scm file containing the package definition.

My question is, if I am developing a package which has dependencies
with newer versions than what is available in the guix repo, how can I
use the guix.scm file to bring in the new version of the dependencies?
 As an example:

Say  my package "my-package" has dependencies d1, d2, d3
where d2 in the current guix package repo is at version 0.1.2 but I
need a later release version 0.1.4; so I tried something like this:

----guix.scm---
(use-modules (guix packages)
   ....)

(define-public d2-0.1.4
   (package
       (name "d2")
       (version "0.1.4")

   ...
)


(define-public my-package
   (package
      (name "my-package")
      (version "0.1")
     ...


     (input (list d1 d2-0.1.4 d3...)
    ....
))

my-package

---end guix.scm---


and if I use

guix shell -f -d ./guix.scm

this does not seem to generate an environment that contains the new
dependency, that is d2 version 0.1.4

I wonder how can this made to work?  Ideally no need to create a
private channel or such..  Thanks for info on this.

Re: Fwd: question on setting up guix.scm for project development

[Pjotr Prins]

It is a good idea. Best way is to create your own packages in a
channel and include those.

On Mon, Nov 14, 2022 at 10:41:58AM -0800, Andy Tai wrote:
> Hi, guix allows setting up an environment containing all the
> dependencies for development of a package; this can be done via a
> guix.scm file containing the package definition.
> 
> My question is, if I am developing a package which has dependencies
> with newer versions than what is available in the guix repo, how can I
> use the guix.scm file to bring in the new version of the dependencies?
>  As an example:
> 
> Say  my package "my-package" has dependencies d1, d2, d3
> where d2 in the current guix package repo is at version 0.1.2 but I
> need a later release version 0.1.4; so I tried something like this:
> 
> ----guix.scm---
> (use-modules (guix packages)
>    ....)
> 
> (define-public d2-0.1.4
>    (package
>        (name "d2")
>        (version "0.1.4")
> 
>    ...
> )
> 
> 
> (define-public my-package
>    (package
>       (name "my-package")
>       (version "0.1")
>      ...
> 
> 
>      (input (list d1 d2-0.1.4 d3...)
>     ....
> ))
> 
> my-package
> 
> ---end guix.scm---
> 
> 
> and if I use
> 
> guix shell -f -d ./guix.scm
> 
> this does not seem to generate an environment that contains the new
> dependency, that is d2 version 0.1.4
> 
> I wonder how can this made to work?  Ideally no need to create a
> private channel or such..  Thanks for info on this.
> 

Re: Fwd: question on setting up guix.scm for project development

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

I think you got it right, I've used thas in the past. Maybe your cli options are out of order? Instead of -f -d, try -D -f. Do you even have d1 or d3 in your current shell? Could they come from outside?

Le 14 novembre 2022 19:41:58 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>Hi, guix allows setting up an environment containing all the
>dependencies for development of a package; this can be done via a
>guix.scm file containing the package definition.
>
>My question is, if I am developing a package which has dependencies
>with newer versions than what is available in the guix repo, how can I
>use the guix.scm file to bring in the new version of the dependencies?
> As an example:
>
>Say  my package "my-package" has dependencies d1, d2, d3
>where d2 in the current guix package repo is at version 0.1.2 but I
>need a later release version 0.1.4; so I tried something like this:
>
>----guix.scm---
>(use-modules (guix packages)
>   ....)
>
>(define-public d2-0.1.4
>   (package
>       (name "d2")
>       (version "0.1.4")
>
>   ...
>)
>
>
>(define-public my-package
>   (package
>      (name "my-package")
>      (version "0.1")
>     ...
>
>
>     (input (list d1 d2-0.1.4 d3...)
>    ....
>))
>
>my-package
>
>---end guix.scm---
>
>
>and if I use
>
>guix shell -f -d ./guix.scm
>
>this does not seem to generate an environment that contains the new
>dependency, that is d2 version 0.1.4
>
>I wonder how can this made to work?  Ideally no need to create a
>private channel or such..  Thanks for info on this.
>

[-- Attachment #2: Type: text/html, Size: 1891 bytes --]

Re: Fwd: question on setting up guix.scm for project development

[Andy Tai]

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

Hi, thanks.

guix shell -D -f guix.scm

did work for me.... I did not see d2 0.1.4 from


guix package --list-installed
or
guix package --list-available
but

pkg-config --modversion d2

did show 0.1.4   So it is there, in this guix shell.

Thanks for all the replies to this question.

On Mon, Nov 14, 2022 at 10:15 PM Julien Lepiller <julien@lepiller.eu> wrote:

> I think you got it right, I've used thas in the past. Maybe your cli
> options are out of order? Instead of -f -d, try -D -f. Do you even have d1
> or d3 in your current shell? Could they come from outside?
>
> Le 14 novembre 2022 19:41:58 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>>
>>
>> ----guix.scm---
>> (use-modules (guix packages)
>>    ....)
>>
>> (define-public d2-0.1.4
>>    (package
>>        (name "d2")
>>        (version "0.1.4")
>>
>>    ...
>> )
>>
>>
>> (define-public my-package
>>    (package
>>       (name "my-package")
>>       (version "0.1")
>>      ...
>>
>>
>>      (input (list d1 d2-0.1.4 d3...)
>>     ....
>> ))
>>
>> my-package
>>
>> ---end guix.scm---
>>
>>

[-- Attachment #2: Type: text/html, Size: 3135 bytes --]

Re: Fwd: question on setting up guix.scm for project development

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

To be clear, guix package always operates on the list of installed packages in your user profile (~/.guix-profile), not packages from your environment. Don't rely on its information to look at what's in a guix shell :)

Le 15 novembre 2022 16:40:05 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>Hi, thanks.
>
>guix shell -D -f guix.scm
>
>did work for me.... I did not see d2 0.1.4 from
>
>
>guix package --list-installed
>or
>guix package --list-available
>but
>
>pkg-config --modversion d2
>
>did show 0.1.4   So it is there, in this guix shell.
>
>Thanks for all the replies to this question.
>
>On Mon, Nov 14, 2022 at 10:15 PM Julien Lepiller <julien@lepiller.eu> wrote:
>
>> I think you got it right, I've used thas in the past. Maybe your cli
>> options are out of order? Instead of -f -d, try -D -f. Do you even have d1
>> or d3 in your current shell? Could they come from outside?
>>
>> Le 14 novembre 2022 19:41:58 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>>>
>>>
>>> ----guix.scm---
>>> (use-modules (guix packages)
>>>    ....)
>>>
>>> (define-public d2-0.1.4
>>>    (package
>>>        (name "d2")
>>>        (version "0.1.4")
>>>
>>>    ...
>>> )
>>>
>>>
>>> (define-public my-package
>>>    (package
>>>       (name "my-package")
>>>       (version "0.1")
>>>      ...
>>>
>>>
>>>      (input (list d1 d2-0.1.4 d3...)
>>>     ....
>>> ))
>>>
>>> my-package
>>>
>>> ---end guix.scm---
>>>
>>>

[-- Attachment #2: Type: text/html, Size: 3625 bytes --]

Re: question on setting up guix.scm for project development

[Ludovic Courtès]

Hi,

Andy Tai <atai@atai.org> skribis:

> ----guix.scm---
> (use-modules (guix packages)
>    ....)
>
> (define-public d2-0.1.4
>    (package
>        (name "d2")
>        (version "0.1.4")
>
>    ...
> )
>
>
> (define-public my-package
>    (package
>       (name "my-package")
>       (version "0.1")
>      ...
>
>
>      (input (list d1 d2-0.1.4 d3...)
>     ....
> ))
>
> my-package
>
> ---end guix.scm--
>
>
> and if I use
>
> guix shell -f -d ./guix.scm
>
> this does not seem to generate an environment that contains the new
> dependency, that is d2 version 0.1.4

‘guix shell -f guix.scm’ generates an environment that contains the
package returned by ‘guix.scm’.

Conversely, ‘guix shell -D -f guix.scm’ produces the development
environment of the package returned by ‘guix.scm’.

HTH!

Ludo’.