1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
2 |
Hash: SHA1
|
3 |
|
4 |
On Fri, 07 Sep 2012 10:50:40 -0400
|
5 |
Ian Stakenvicius <axs@g.o> wrote:
|
6 |
> On 07/09/12 07:45 AM, Ciaran McCreesh wrote: |
7 |
> > [ Snip! ] Note also how the foo-related things, the bar-related |
8 |
> > things etc cannot be grouped together by their fooness or barness, |
9 |
> > but are rather grouped by their DEPENDness and RDEPENDness. |
10 |
> > |
11 |
> > [ Snip! ] |
12 |
> > |
13 |
> > So here's what DEPENDENCIES solves: |
14 |
> > |
15 |
> > Firstly, it allows developers to group together foo-related |
16 |
> > dependencies and bar-related dependencies by their fooness and |
17 |
> > barness, not by their role. [ Snip! ] *** It does it by replacing |
18 |
> > the concept of "a package has build *** dependencies, run |
19 |
> > dependencies, etc" with "a package has *** dependencies, and each |
20 |
> > dependency is applicable at one or more of *** build time, run tme, |
21 |
> > etc". |
22 |
> |
23 |
> And this is the specific point that I don't like about DEPENDENCIES |
24 |
> versus *DEPEND. As a developer, I personally find it much more |
25 |
> straight-forward to fill in the deps needed for each role, rather than |
26 |
> specifying the role(s) that each dep will play a part in. |
27 |
|
28 |
Have you tried doing both? You may find you're just arguing from
|
29 |
familiarity, and that after having worked the other way for a few
|
30 |
packages, that the advantages become clearer.
|
31 |
|
32 |
The wide-spread use of hacks like COMMON_DEPEND are a pretty strong
|
33 |
indication that people *do* think in something closer to a
|
34 |
DEPENDENCIES-like fashion. In particular, I find it hard to believe
|
35 |
that you think "ok, so I've got a build dependency upon
|
36 |
>=cat/pkg-2.3[foo]" and then independently work out "ok, I've got a run |
37 |
>dependency upon >=cat/pkg-2.3[foo]". |
38 |
|
39 |
- --
|
40 |
Ciaran McCreesh
|
41 |
-----BEGIN PGP SIGNATURE-----
|
42 |
Version: GnuPG v2.0.19 (GNU/Linux)
|
43 |
|
44 |
iEYEARECAAYFAlBKC6cACgkQ96zL6DUtXhG94gCgmXP0C+nAItSnCTIMoeJHzqzK
|
45 |
AyYAniXFZR5mJrBtuGI10dWt0nuJFhwc
|
46 |
=vZBn
|
47 |
-----END PGP SIGNATURE----- |