ôòøguix build --sourceôòù should be changed to return the result of
applying
that ôòøpatchôòù phase to the upstream tarball. WDYT?
Sounds right.
in that it provides the /complete/ build recipe that led to the
binaryôòóôòücompleteôòý means that it includes build scripts, p
Ludovic Courtès said:
> Yes, I understand this, but my question was more about how this occurs
> technically.
>
> My understanding is that Debian-based distros provide the unmodified
> upstream source, with a debian/patches tree containing patches they
> apply. Do I get it right?
Ah, I see. In th
Op Sat, 14 Sep 2013 15:01:13 +0200
schreef l...@gnu.org (Ludovic Courtès):
> My understanding is that Debian-based distros provide the unmodified
> upstream source, with a debian/patches tree containing patches they
> apply. Do I get it right?
For gNewSense we do as follows. If the software reco
"Jason Self" skribis:
> Ludovic Courtès asked:
>> But, what does "source code" mean here? Does it mean the source that's
>> made available using the distro tools, such as 'apt-get source'?
>
> That's my understanding of it.
OK.
Again, I’d like to stress that Guix goes way further than this: an
k...@freefriends.org (Karl Berry) skribis:
> So, do we want ‘guix build --source’ to return the already-patched,
> FSDG-compliant source?
>
> It should return exactly the sources which actually got built -- which I
> gather, though I'm not sure, is not necessarily the same as "unmodified
>
