Re: Rethinking propagated inputs?

2021-09-05 Thread Liliana Marie Prikler
Am Samstag, den 04.09.2021, 17:50 -0700 schrieb Sarah Morgensen: > Hi Liliana, > > (Efraim, I've Cc'd you since you're working on re-doing Rust inputs.) > > Liliana Marie Prikler writes: > > > Does anyone have an idea how we should handle propagations for the > > sake of pkg-config? Perhaps we

Re: Rethinking propagated inputs?

2021-09-05 Thread Bengt Richter
Hi, On +2021-09-05 09:36:30 +0200, Liliana Marie Prikler wrote: > Am Samstag, den 04.09.2021, 17:50 -0700 schrieb Sarah Morgensen: > > Hi Liliana, > > > > (Efraim, I've Cc'd you since you're working on re-doing Rust inputs.) > > > > Liliana Marie Prikler writes: > > > > > Does anyone have an i

Re: Rethinking propagated inputs?

2021-09-05 Thread Attila Lendvai
> > What do you think of "build-propagated-inputs"? > > We don't call things build-inputs here in Guix land, that's a no-no :P potentially worthless two cents from a newcomer's perspective: 'build-time' and 'run-time' are well established concepts in the wider community. if i were reading 'linked

Guix Jargon File (WAS: Rethinking propagated inputs?)

2021-09-05 Thread Liliana Marie Prikler
Hi, Am Sonntag, den 05.09.2021, 11:50 +0200 schrieb Bengt Richter: > > We don't call things build-inputs here in Guix land, that's a no-no > > :P > > Is there an official guix jargon file or glossary file or texi file > or wikimedia/wiktionary/wikipedia clone on gnu.org that non- > cognoscenti c

Re: Rethinking propagated inputs?

2021-09-05 Thread Julien Lepiller
All inputs of a package are build-time, whether normal, native or propagated. The result may reference some of them, and these references are the run-time dependencies. native-inputs are usually buill-time only, because they are usually programs that are run during the build (hence the need for

Re: Guix Jargon File (WAS: Rethinking propagated inputs?)

2021-09-05 Thread Bengt Richter
Hi Liliana, Thank you for starting this renamed thread (as I should have done). I think a people who are just looking at _maybe_ installing guix should have an easy way to look up terms they haven't seen before. But really I am more interested in promoting the idea of a snippet-quoting conventio

Re: Guix Jargon File (WAS: Rethinking propagated inputs?)

2021-09-05 Thread Liliana Marie Prikler
Hi, Am Sonntag, den 05.09.2021, 16:54 +0200 schrieb Bengt Richter: > Hi Liliana, > > Thank you for starting this renamed thread (as I should have done). > > I think a people who are just looking at _maybe_ installing guix > should have an easy way to look up terms they haven't seen before. Perso

Re: Guix Jargon File (WAS: Rethinking propagated inputs?)

2021-09-05 Thread Jonathan McHugh
Hi Bengt, I believe that a collection of regular expressions for recognising starting block and closing block for differing formats. It would for instance become political making a choice between (say): * -a-dangerous-pair-of-scissors--8<--ouch- ; * an Orgmode output; a GemText block; * somebody

Re: Rethinking propagated inputs?

2021-09-05 Thread Maxime Devos
Liliana Marie Prikler schreef op za 04-09-2021 om 20:24 [+0200]: > Hi Guix, > > some while ago we made the decision to propagate inputs, that are > mentioned in pkg-config files, the rationale being that those > propagated inputs will be needed in packages in order to compile. This > has saved us

Re: Rethinking propagated inputs?

2021-09-05 Thread Liliana Marie Prikler
Hi Am Sonntag, den 05.09.2021, 18:17 +0200 schrieb Maxime Devos: > Liliana Marie Prikler schreef op za 04-09-2021 om 20:24 [+0200]: > > Hi Guix, > > > > some while ago we made the decision to propagate inputs, that are > > mentioned in pkg-config files, the rationale being that those > > propagat

Re: Rethinking propagated inputs?

2021-09-05 Thread Maxime Devos
Liliana Marie Prikler schreef op zo 05-09-2021 om 18:50 [+0200]: > [...] > > (Feel free to suggest a more concise name.) > Since "propagated" is already given by propagated-inputs, what about > simply having #:by? > E.g. something like: [...] > (define glib > (package > (name "glib") >

Re: Rethinking propagated inputs?

2021-09-05 Thread Liliana Marie Prikler
Am Sonntag, den 05.09.2021, 21:18 +0200 schrieb Maxime Devos: > [...] > [Liliana Marie Prikler schreef op zo 05-09-2021 om 18:50 [+0200]:] > > This does cause problems with language bindings though, > > e.g. pygobject, as those also propagate the package in question and > > can't be neatly separate

Re: Rethinking propagated inputs?

2021-09-05 Thread Maxime Devos
Liliana Marie Prikler schreef op zo 05-09-2021 om 21:37 [+0200]: > > > I must admit that this solution appears to have some surface > > > elegance, but what exactly would go in the "build" output of a > > > package? You mentioned pkg-config files (obviously), but those > > > don't suffice to actua

Re: Rethinking propagated inputs?

2021-09-05 Thread Liliana Marie Prikler
Am Sonntag, den 05.09.2021, 22:27 +0200 schrieb Maxime Devos: > Liliana Marie Prikler schreef op zo 05-09-2021 om 21:37 [+0200]: > > > > I must admit that this solution appears to have some surface > > > > elegance, but what exactly would go in the "build" output of a > > > > package? You mentione

Re: Guix Jargon File (WAS: Rethinking propagated inputs?)

2021-09-05 Thread Bengt Richter
Hi Jonathan, Thanks for the TXR reference, I will have to look into it. Just on the basis of the author name "Kaz Kylheku" I would check it out. I have encountered his posts 'way in the past, and they were always intelligent and interesting. (If he is older than me, I'd like to know more about hi

Re: Guix Packaging Meetup - This Saturday from 14:00 EST (18:00 PM UTC)

2021-09-05 Thread jgart
On Sat, 28 Aug 2021 00:50:26 +0530 Arun Isaac wrote: > > > I've started to use tz to keep track of timezones. > > > > https://github.com/oz/tz > > > > It's a nice cli app written in golang. > > Thank you! :-) I was looking for something like this. > alias tz='TZ_LIST="Africa/Nairobi,Europe/Ams