From: konsolebox <konsolebox@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] What are eblits?
Date: Fri, 27 May 2016 22:26:35 +0800 [thread overview]
Message-ID: <CAJnmqwbLWuhyKd4dGtc7QA=pTnLHu3rrPd3OFZ0NQ2f7ZEvoGQ@mail.gmail.com> (raw)
In-Reply-To: <CAATnKFBqML9iTvZB=++3GrMsHdTuHPmCLCZfje17WySOhhUC2Q@mail.gmail.com>
On Fri, May 27, 2016 at 9:28 AM, Kent Fredric <kentfredric@gmail.com> wrote:
> That said, its a very confusing system to get your head around,
> because its *basically* yet another "mixin" system like "inherit", but
> done in bash, which itself is a rather strange language to be doing
> something as complicated as mixins.
This concept is new to me as well, but after seeing the code with `cat
/usr/portage/sys-libs/glibc/glibc-2.17.ebuild` it didn't even take me
5 or 10 minutes to understand it. I find the implementation safe
enough if used properly. The core functions also seem stable, besides
some parts which aren't quoted, although commonly normal in ebuilds.
This is all about loading common functions to your ebuilds, and
there's nothing really dangerous in it.
--
konsolebox
next prev parent reply other threads:[~2016-05-27 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 22:28 [gentoo-dev] What are eblits? rindeal
2016-05-27 1:28 ` Kent Fredric
2016-05-27 14:26 ` konsolebox [this message]
2016-05-29 1:11 ` Joshua Kinard
2016-05-29 6:02 ` Rich Freeman
2016-05-29 8:25 ` Ulrich Mueller
2016-05-29 12:29 ` Rich Freeman
2016-05-29 14:20 ` Joshua Kinard
2016-05-27 1:56 ` [gentoo-dev] " Duncan
2016-05-27 13:06 ` [gentoo-dev] " Ciaran McCreesh
2016-05-27 17:35 ` [gentoo-dev] " rindeal
2016-05-28 5:07 ` Kent Fredric
2016-05-28 18:40 ` Duncan
2016-05-29 1:05 ` [gentoo-dev] " Joshua Kinard
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='CAJnmqwbLWuhyKd4dGtc7QA=pTnLHu3rrPd3OFZ0NQ2f7ZEvoGQ@mail.gmail.com' \
--to=konsolebox@gmail.com \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox