Thanks again for the reply simon!
zimoun writes:
> Hi,
>
> On Mon, 30 Nov 2020 at 14:39, Brandon Ellington wrote:
>
| package of interest | guix commit | status |
|-+--+|
| python-matplotlib | "7e06086522" | bad|
| python-pandas
zimoun writes:
> You might be interested by the Efraim’s talk «Just build it with Guix»
> from the online Guix Day:
Yes this is extremely useful - thanks!
Hi all!
Was finally able to hack something that
works! See below:
zimoun writes:
>
> (And I am still interested by the answer of «is it possible to get the
> metadata of the inputs in phases?» :-))
>
Yes it's possible. The trick is to use
"this-package" which can *only* be used inside a
package
Hi Pierre,
On Tue, 01 Dec 2020 at 10:10, Pierre Neidhardt wrote:
> So here is my final, hopefully fully-functioning version then:
I am testing it. Thanks!
Cheers,
simon
Hi,
On Tue, 01 Dec 2020 at 13:28, Phil wrote:
> I could instead run my unit tests against my git clone, but then you're
> not testing what you will deliver, you're testing the source code that
> will be packaged, not the package itself. The unit tests may fail if
> run on the package itself.
>
Thanks again zimoun for your comments.
zimoun writes:
> I am not sure to understand what you mean. Installing always means
> “fixed at package@version”. I should miss something with your
> workflow.
So using pip in 'editable' mode installs your git clone via softlinks as a
package.
It doesn'
Hi,
On Mon, 30 Nov 2020 at 15:04, Phil wrote:
> I 100% agree it's a bad idea to mix packagers, but pip install's use-cases go
> beyond the need to do fixed installs of package@version, provided by
> Guix.
I am not sure to understand what you mean. Installing always means
“fixed at package@versi
Hi,
On Mon, 30 Nov 2020 at 14:39, Brandon Ellington wrote:
>>> | package of interest | guix commit | status |
>>> |-+--+|
>>> | python-matplotlib | "7e06086522" | bad|
>>> | python-pandas | ce2cfcabfc | bad|
>>> | python-networkx | 2
Hi,
On Tue, 01 Dec 2020 at 12:13, "Bonface M. K." wrote:
>> What do you want? Get the list of inputs and their metadata when typing
>> “guix install foo”? And this list becoming part of the outputs? Or
>> simply get somehow the list of inputs and their metadata? Which is
>> straightforward.
Hi Efraim!
Efraim Flashner writes:
[...]
>> Notice that the version, home page and description
>> are repeated across rows. Herein lies my question:
>> How would you fetch the details of the inputs(like
>> version, home-page, description) etc etc from a
>> modifed phase. Do I need to create a cl
Hi!
zimoun writes:
[...]
> …I am not convinced it is the right level to extract the
> information you need since ’input’ is, e.g.,
>
> ;;; (("source" .
> "/gnu/store/hbdalsf5lpf01x4dcknwx6xbn6n5km6k-hello-2.10.tar.gz"))
> ;;; (("grep" . "/gnu/store/yhqc5imq7sn2sf9f48dj4gk12y4kw4s4-grep-3.4"
Ah! That's good to know!
So here is my final, hopefully fully-functioning version then:
--8<---cut here---start->8---
(defvar ambrevar/known-mailing-list-archives
'(("help-guix@gnu.org" . "guix")
("guix-de...@gnu.org" . "guix")
("debbugs.gnu.org" . "
Hi!
Julien Lepiller writes:
> The reason you always get the same data is because
> you're assigning "name" inside the sexp
> (build-side), but you're using it inside tge
> unquote (host-side), so it refers to the name of
> the package you're building.
>
Ah yes! I see that now. Silly me ~.~
> I
13 matches
Mail list logo
