public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: "Andreas K. Huettel" <dilfridge@gentoo.org>
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call for Council Agenda Items - 14 Oct 2014
Date: Mon, 13 Oct 2014 14:54:56 +0200	[thread overview]
Message-ID: <21563.52128.209803.666013@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20141013110439.1809432d@pomiot.lan>

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]

>>>>> On Mon, 13 Oct 2014, Michał Górny wrote:

> 2. Dependency updates [2] are stuck midway games. With no help from
> games team, the fact that most of the current dependencies don't
> make sense and that most of the games are proprietary, you shouldn't
> expect much sane progress anytime soon. Likely we're just going to
> end up updating the current dependencies knowing they're likely
> wrong.

"Il meglio è l'inimico del bene." -- Voltaire

You could start with the dependencies currently in ebuilds, and in
addition use tools like scanelf or lddtree for scanning the binaries
installed by the package. (Or even the old tools for porting packages
to modular X [4] could be used; it's a very similar task.)

IMHO this would give you a very reasonable approximation of the true
dependencies. Some details (like correct USE dependencies on libSDL)
might be missed, but these can be fixed later. In any case, the
updated dependencies will be an improvement over the current ones,
so I won't see any of these small imperfections as a blocker.

Ulrich


> [1]:https://bugs.gentoo.org/show_bug.cgi?id=498010
> [2]:https://wiki.gentoo.org/wiki/Multilib_porting_status#Dependency_update_status
> [3]:https://bugs.gentoo.org/show_bug.cgi?id=513718

[4] https://www.gentoo.org/proj/en/desktop/x/x11/porting-modular-x-howto.xml

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2014-10-13 12:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGfcS_m5cWLG_94-KMqaGef5JU-zr8-oJzjd4Q8QSAk=34QeeQ@mail.gmail.com>
2014-10-01  8:43 ` [gentoo-project] Re: [gentoo-dev-announce] Call for Council Agenda Items - 14 Oct 2014 Ulrich Mueller
2014-10-01 17:30 ` [gentoo-project] " Rich Freeman
2014-10-02 23:06   ` Michał Górny
2014-10-03 20:23 ` [gentoo-project] Re: [gentoo-dev-announce] " Andreas K. Huettel
2014-10-03 22:41   ` Rich Freeman
2014-10-04 12:30     ` Andreas K. Huettel
2014-10-04 15:04       ` Michał Górny
2014-10-13  9:04   ` Michał Górny
2014-10-13  9:59     ` Pacho Ramos
2014-10-13 10:06       ` Michał Górny
2014-10-13 10:18         ` Pacho Ramos
2014-10-13 12:54     ` Ulrich Mueller [this message]
2014-10-13 12:59       ` Michał Górny
2014-10-13 18:09         ` Rich Freeman
2014-10-13 14:44       ` Ciaran McCreesh

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=21563.52128.209803.666013@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=dilfridge@gentoo.org \
    --cc=gentoo-project@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