Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-02 Thread William L. Thomson Jr.
On Tuesday, November 1, 2016 1:31:55 AM EDT Michał Górny wrote: > > 1. How often do you find '~' useful? Do you think there should be > additional operators that ignore revision part? IMHO, this one should be a requirement anytime a project/package is split between multiple ebuilds. This is

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-02 Thread Sergei Trofimovich
On Wed, 2 Nov 2016 07:43:04 +0100 Michał Górny wrote: > On Tue, 1 Nov 2016 23:09:25 + > Sergei Trofimovich wrote: > > > On Tue, 1 Nov 2016 14:16:18 +0100 > > Michał Górny wrote: > > > > > However, while at it I should > > > point

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-02 Thread Daniel Campbell
On 10/31/2016 05:31 PM, Michał Górny wrote: > Hello, everyone. Answering inline to help context. > > I would like to work on a major version depedencny specification > improvements as part of the next EAPI. For this reason, I'd like to > first gather some research on how developers are using

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-02 Thread Michał Górny
On Tue, 1 Nov 2016 23:09:25 + Sergei Trofimovich wrote: > On Tue, 1 Nov 2016 14:16:18 +0100 > Michał Górny wrote: > > > However, while at it I should > > point out that the spec doesn't really cover pure-DEPEND :=, so there > > is no guarantee that

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-01 Thread Sergei Trofimovich
On Tue, 1 Nov 2016 14:16:18 +0100 Michał Górny wrote: > On Tue, 1 Nov 2016 09:29:09 + > Sergei Trofimovich wrote: > > > > 4. What are the common tasks that you find unnecessarily complex / > > > lengthy with the current version specifications? > > >

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-01 Thread Andreas K. Huettel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Michał, > > Therefore, I would like to ask the following questions: > > 1. How often do you find '~' useful? Do you think there should be > additional operators that ignore revision part? > Very useful for virtuals (especially perl virtuals

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-01 Thread Michał Górny
On Tue, 1 Nov 2016 09:29:09 + Sergei Trofimovich wrote: > > 4. What are the common tasks that you find unnecessarily complex / > > lengthy with the current version specifications? > > Problem 1: > > Sometimes upstream decides that one of their dependencies > is broken on

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-01 Thread Michael Orlitzky
On 10/31/2016 08:31 PM, Michał Górny wrote: > > 4. What are the common tasks that you find unnecessarily complex / > lengthy with the current version specifications? Slotted version ranges, for example: berkdb? ( || ( sys-libs/db:5.3 sys-libs/db:5.1

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-11-01 Thread Sergei Trofimovich
On Tue, 1 Nov 2016 01:31:55 +0100 Michał Górny wrote: Haskell package ecosystem (hackage) encourages upper version bounds and strict version bounds on dependencies: http://pvp.haskell.org/ Most of dependencies look like: >=foo-1.3 =bar-2.1 =baz-2.1 =baz-2.9 Therefore, I

Re: [gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-10-31 Thread Ian Stakenvicius
On 31/10/16 08:31 PM, Michał Górny wrote: > Hello, everyone. > > I would like to work on a major version depedencny specification > improvements as part of the next EAPI. For this reason, I'd like to > first gather some research on how developers are using the current > system, what they find

[gentoo-dev] [RFC] Problems and limitations of the current version dependency specs

2016-10-31 Thread Michał Górny
Hello, everyone. I would like to work on a major version depedencny specification improvements as part of the next EAPI. For this reason, I'd like to first gather some research on how developers are using the current system, what they find efficient and what they find cumbersome. Therefore, I