From: ng0 <ng0@infotropique.org>
To: guix-devel@gnu.org
Subject: Re: food for thought: ebuild importer?
Date: Thu, 10 Aug 2017 09:05:05 +0000 [thread overview]
Message-ID: <20170810090505.ntnjm7ku7tk2ivhz@abyayala> (raw)
In-Reply-To: <20170810090153.jitvz6pmk4betsy5@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
ng0 transcribed 2.1K bytes:
> So a very long time ago I was wondering: What if we could
> take for example Gentoo's portage (and overlays) and process
> ebuilds with an importer? There is software on there which does
> not fall into our Guidelines by licenses, but there are many
> more receipes on there we can make use of.
>
> Ultimately we'll have the QA to check if it's compatible etc.
> ebuild format changes every 2 years (in theory, sometimes stable
> formats changed even between these 2 years) as another format gets
> added.
Oh, and because of the (hopefully most of the time correct) field for
licenses we could even filter out incompatible licenses.
> So we would "just" need an ebuild-reader which would process this
> from .ebuild (there's also .eclass we need to consider) to guix package.
>
> We could do the same with PKGBUILD from the Archlinux based systems
> and maybe other formats of other systems.
>
> Or is this an idea which could never be in master because of this
> systems providing receipes for software which is not fully compatible
> with the Guidelines?
>
> Just a "what if" question…
> --
> ng0
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://n0is.noblogs.org/my-keys
> https://www.infotropique.org https://krosos.org
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-10 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 9:01 food for thought: ebuild importer? ng0
2017-08-10 9:05 ` ng0 [this message]
2017-08-10 19:15 ` Joshua Branson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170810090505.ntnjm7ku7tk2ivhz@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.