Am 09.09.21 um 11:48 schrieb Ludovic Courtès:
We’d have to check how they do it in Nix. Basically, it’s about
reversing things: currently, everything goes to “out”, and a tiny bit
goes to “lib”. Here, it’d be the other way around: “out” would contain
only binaries and doc (unless there’s a
Hi Liliana,
Liliana Marie Prikler skribis:
> Am Donnerstag, den 09.09.2021, 00:12 +0200 schrieb Ludovic Courtès:
[...]
>> It would be great if the ‘Requires’ field of .pc files could specify
>> absolute file name; it would no longer be necessary to set
>> PKG_CONFIG_PATH, and thus propagation
On Thu, 09 Sep 2021 at 00:12, Ludovic Courtès wrote:
> Maxime Devos skribis:
>> (define glib
>> (package
>> (name "glib")
>> (outputs '("out" ; everything
>> "bin" ; glib-mkenums ... depends on Python
>> "build")) ; glib-2.0.pc
>>
Hi,
Am Donnerstag, den 09.09.2021, 00:12 +0200 schrieb Ludovic Courtès:
> Hi,
>
> Maxime Devos skribis:
>
> > For packages using pkg-config, I had the following scheme in mind:
>
> As a reminder to everyone, pkg-config is just one of the reasons for
> propagating inputs, probably not the main
Hi,
Maxime Devos skribis:
> For packages using pkg-config, I had the following scheme in mind:
As a reminder to everyone, pkg-config is just one of the reasons for
propagating inputs, probably not the main one numerically speaking.
> A package that has .pc files puts them into a separate
Hi,
September 8, 2021 12:18 AM, "Liliana Marie Prikler"
wrote:
> Hi,
>
> Am Dienstag, den 07.09.2021, 12:01 -0700 schrieb Sarah Morgensen:
>
>> [...]
>>
>> However, IMO it doesn't make sense to automatically install these in
>> a profile when installing that package. If you're installing a
Hi,
Am Dienstag, den 07.09.2021, 12:01 -0700 schrieb Sarah Morgensen:
> [...]
>
> However, IMO it doesn't make sense to automatically install these in
> a profile when installing that package. If you're installing a
> source-only package, you likely don't want all the transitive
> dependencies
Maxim Cournoyer writes:
> It seems the original issue pointed at was somewhat misguided; is there
> still something to be fixed about propagated inputs? It seems the
> discussion has moved toward handling propagated inputs for the use of
> pkg-config.
>
> What are the current problems with it,
Hello, good plan!
Liliana Marie Prikler writes:
> At this point the question then becomes what to name this "build"
> output and what to put into it besides pkg-config stuff.
In Debian, it's a "dev" package, includes .h (C headers), .pc, .a
(static libraries).
> Particularly in the land of
Liliana Marie Prikler schreef op zo 05-09-2021 om 23:10 [+0200]:
> 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
Hi,
Am Montag, den 06.09.2021, 14:07 -0400 schrieb Maxim Cournoyer:
> Hello,
>
> Liliana Marie Prikler writes:
>
> > 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,
> > > >
> > >
Hello,
Liliana Marie Prikler writes:
> 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
Hi,
On Sat, 04 Sep 2021 at 20:24, Liliana Marie Prikler
wrote:
> Does anyone have an idea how we should handle propagations for the sake
> of pkg-config? Perhaps we could add "linked-inputs", which are added
> when building packages and environments when not using --ad-hoc, but
> not when
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
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
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
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
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")
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
> >
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
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;
*
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.
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
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
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
> > 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
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
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
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 could add "linked-inputs", which are added
> when building packages and
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 some typing, but at a cost. For instance, it is now no
longer possible to
30 matches
Mail list logo
