Hey I just want to throw out there that I have a very WIP go module importer[1]
sitting on my channel. It uses the proxy.golang.org[2] api to fetch the
module's dependencies and source. The single module importer works for the most
part but I need to fix it so that the recursive importer doesn't
Em 28/01/2021 13:03, Ludovic Courtès escreveu:
> IMO, ‘guix import’ does not “steer users towards obtaining any nonfree
> information” any more than wget does. It’s a tool for packagers that
> returns a package definition or template thereof, and it’s up to the
> packager to decide what to do with
Hi,
adfeno--- via skribis:
> If by vendoring we mean bundling and also make users fetch data from places
> not explicitly committed to the GNU FSDG, then allow me to jump in to add
> some important notes.
>
> Em 27/01/2021 11:31, Katherine Cox-Buday escreveu:
>> As a packager for a distributio
If by vendoring we mean bundling and also make users fetch data from places not
explicitly committed to the GNU FSDG, then allow me to jump in to add some
important notes.
Em 27/01/2021 11:31, Katherine Cox-Buday escreveu:
> As a packager for a distribution, I dislike vendoring because of the
>
Katherine Cox-Buday writes:
> Hello again, François! I've redirected this thread to guix-devel, and
> the bug since we've begun discussing implementation details.
>
> JOULAUD François writes:
>
>> First is to use vendored dependencies (when upstream provides them). This
>> one has the merits of
Hello again, François! I've redirected this thread to guix-devel, and
the bug since we've begun discussing implementation details.
JOULAUD François writes:
> First is to use vendored dependencies (when upstream provides them). This
> one has the merits of simplicity (as we just have to download
