From: Richard Yao <ryao@gentoo.org>
To: hasufell <hasufell@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, games@gentoo.org, mgorny@gentoo.org
Subject: [gentoo-dev] Re: New eclass: games-bin (review/comments)
Date: Tue, 26 Mar 2013 18:15:38 -0400 [thread overview]
Message-ID: <51521E0A.8000506@gentoo.org> (raw)
In-Reply-To: <514E1667.8030604@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On 03/23/2013 04:53 PM, hasufell wrote:
> After packaging the complete humble bundle last time I noticed a bit
> of code duplication.
> Nothing serious, but I still think there could be a small eclass
> making things easier.
>
> Especially the "remove_bundled_libs" function and the is useful IMO
> and allows to easily remove those things.
> The GAMES_PRESERVE_BUNDLED_LIBS array would allow to preserve libs,
> e.g. stuff like "libbass" which is not present in the tree and even
> GAMES_PRESERVE_BUNDLED_LIBS_amd64 (in case we have a 32bit only game
> and there are no multilib versions for some of those libs).
>
> It also works well with a "bundled-libs" useflag (see
> games-bin_src_prepare), because it can happen that binary games break
> while the tree is moving forward with library versions, or that system
> libraries create weird blockers for the user or even cause runtime
> breakage (which happened with the editor of games-rpg/grimrock wrt
> #454934).
>
> Most bin games use some functions from unpacker.eclass, so it is
> inherited and used in games-bin_src_unpack by default.
>
> I was also thinking about some check-reqs thing, but it's probably
> better that is handled explicitly.
>
>
> If you have suggestions or if you think that approach sucks, please
> tell me.
>
If it works, I see no reason not to commit it. It has my okay.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
prev parent reply other threads:[~2013-03-26 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 20:53 [gentoo-dev] New eclass: games-bin (review/comments) hasufell
2013-03-26 22:15 ` Richard Yao [this message]
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=51521E0A.8000506@gentoo.org \
--to=ryao@gentoo.org \
--cc=games@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hasufell@gentoo.org \
--cc=mgorny@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