Hi Hartmut,
> let's pick up on this issue and systematically design the test-cases to
> benchmark the proposed solutions. I already prepared a test-script to
> simplify this and will provide a full description as later.
Thank you for picking up the work on this!
In all of the tests do we only care about the reported value of
site-packages? Should the tests include loading non-trivial packages
that have other Python packages as dependencies?
> 2.3 Installed package *without setting the environment variables!*
>
> guix package -i python && ~/.guix-profile/bin/python3 testit
> --> Expected outcome: site-packages from ~/.guix-profile/
> --> Shall this work, too? Is it nice-to-have or useless?
2.3b is to install the package into a separate profile with
guix package -p /path/to/somewhere -i python
> 2.4 running from /gnu/store (directly)
>
> $(readlink -f ~/.guix-profile/bin/python3) testit
> --> Expected outcome: site-packages from /gnu/store
> --> What is the expected outcome? What is the expected
>
> 2.5 running from /gnu/store (via link)
>
> ln -s $(readlink -f ~/.guix-profile/bin/python3)
> /tmp/test-guix-pythonA.exe ;
> /tmp/test-guix-pythonA.exe testit
> --> Expected outcome: site-packages from /gnu/store
I think these two cases should yield the same result.
> 2.6 Installed in GuixSD
>
> --> Do we need to test this? Or is this already covered by one of
> the other cases?
I don’t think we need to test this as GuixSD does not have any special
behaviour for Python and the system profile is just another profile.
This would be the same as 2.3b.
--
Ricardo
