From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] minimalistic emerge
Date: Fri, 8 Aug 2014 22:14:04 -0400 [thread overview]
Message-ID: <CAGfcS_=EhSOCkQ1vKx8_O_jW9bDGpUX6UGNypkmwmoZayi9-=A@mail.gmail.com> (raw)
In-Reply-To: <53E5302E.7050401@gentoo.org>
On Fri, Aug 8, 2014 at 4:16 PM, Ian Stakenvicius <axs@gentoo.org> wrote:
> I don't think we have any sort of tree-wide policy on this either, do
> we? Although I believe common sense says it's a good idea (and i hope
> most devs do this) to put a minver on a dependency atom if there was
> any ebuild with an older version in the tree within the last year.
There is no reason not to specify a version constraint if you're aware of it.
However, I wouldn't expect devs to go digging around in cvs for
year-old package versions to test against them. If upstream happens
to say it requires foo-1.5, by all means just take their word for it
and list it, but more often than not they don't bother to test old
versions either or note when the APIs they use were introduced.
Rich
next prev parent reply other threads:[~2014-08-09 2:14 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
2014-08-08 19:56 ` Kent Fredric
2014-08-08 20:16 ` Ian Stakenvicius
2014-08-09 2:14 ` Rich Freeman [this message]
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='CAGfcS_=EhSOCkQ1vKx8_O_jW9bDGpUX6UGNypkmwmoZayi9-=A@mail.gmail.com' \
--to=rich0@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