From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] minimalistic emerge
Date: Fri, 08 Aug 2014 15:47:57 -0400 [thread overview]
Message-ID: <53E5296D.30200@gentoo.org> (raw)
In-Reply-To: <20140808193433.25388.qmail@stuge.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 08/08/14 03:34 PM, Peter Stuge wrote:
> Kent Fredric wrote:
>> dependencies are forward specifications from upstream telling us
>> what their software needs to function properly.
>
> Unfortunately that's not the full story. :\
>
> ebuilds often (for me) have artificial dependencies, when the
> actual version required is too old to be in the tree, but maybe not
> too old to be installed on an existing system.
>
> I think it's bad policy to lie about dependencies in ebuilds for
> the sole reason of only ever depending on versions which actually
> exist in the same snapshot. It's a too simplistic model of
> reality.
>
For the most part I don't think that happens very often; usually if
all stable versions of a dependency can satisfy a package's needs then
there isn't any minimum version specification (or the minimum version
specification hasn't actually been updated in an ebuild's *DEPEND,
despite the older versions having been removed).
The main exception to this is the work done related to gx86-multilib
(as for obvious reasons the multilib ebuilds are needed to supply
multilib dependencies), and the refactoring that mgorny did a few
weeks back to fix the EAPI<5 USE_EXPAND+IUSE_IMPLICIT undefined
behaviour issue.
That said, even if dependency atoms allow the older, no-longer-in-tree
versions to satisfy a package's needs, as I said earlier I don't think
any dev has the time and resources to test against anything older than
latest-stable, and definitely not anything that's no longer in the tree.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlPlKW0ACgkQ2ugaI38ACPDAewD/ebk6WQa4pA4VJQkpiXf2Ch/R
uGz0HRy6/Y17eSxDL3wA/2gD8ciNsVWkIV6/kLGwwVXGItLL07A3OXITGLE1U8+N
=EBWi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-08-08 19:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:12 [gentoo-dev] minimalistic emerge Igor
2014-08-08 13:22 ` Ciaran McCreesh
2014-08-08 15:23 ` Igor
2014-08-08 15:36 ` hasufell
2014-08-08 15:53 ` Igor
2014-08-08 15:45 ` Ian Stakenvicius
2014-08-08 16:27 ` Igor
2014-08-08 16:40 ` Homer Parker
2014-08-08 17:26 ` Igor
2014-08-08 17:32 ` Homer Parker
2014-08-08 17:30 ` Ian Stakenvicius
2014-08-09 9:34 ` "Paweł Hajdan, Jr."
2014-08-09 15:25 ` Igor
2014-08-13 7:54 ` [OT] " Tom Wijsman
2014-08-08 16:31 ` Rich Freeman
2014-08-08 13:23 ` hasufell
2014-08-08 13:32 ` Jeroen Roovers
2014-08-08 15:14 ` Alan McKinnon
2014-08-13 8:13 ` Tom Wijsman
2014-08-08 15:51 ` Kent Fredric
2014-08-08 16:58 ` Igor
2014-08-08 17:29 ` Kent Fredric
2014-08-08 20:52 ` Igor
2014-08-08 21:33 ` Kent Fredric
2014-08-08 21:39 ` Ian Stakenvicius
2014-08-08 21:43 ` Kent Fredric
2014-08-09 14:56 ` Igor
2014-08-09 15:12 ` Chris Reffett
2014-08-09 17:10 ` Ciaran McCreesh
2014-08-13 8:20 ` Tom Wijsman
2014-08-13 13:17 ` hasufell
2014-08-09 19:30 ` Jeroen Roovers
2014-08-09 15:44 ` Chris Reffett
2014-08-09 15:46 ` Chris Reffett
2014-08-09 15:58 ` Chris Reffett
2014-08-08 19:34 ` Peter Stuge
2014-08-08 19:47 ` Ian Stakenvicius [this message]
2014-08-08 19:56 ` Kent Fredric
2014-08-08 20:16 ` Ian Stakenvicius
2014-08-09 2:14 ` Rich Freeman
2014-08-09 8:30 ` Peter Stuge
2014-08-08 21:04 ` Johannes Huber
2014-08-13 8:25 ` Tom Wijsman
2014-08-09 3:07 ` [gentoo-dev] " Duncan
2014-08-09 8:34 ` Peter Stuge
2014-08-09 11:03 ` Duncan
2014-08-09 11:06 ` hasufell
2014-08-09 12:16 ` Ambroz Bizjak
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=53E5296D.30200@gentoo.org \
--to=axs@gentoo.org \
--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