| 1 |
On Tue, 14 Jun 2011 05:58:56 +0200 |
| 2 |
Jeroen Roovers <jer@g.o> wrote: |
| 3 |
|
| 4 |
> Judging from [1], a couple of thousands of ebuilds DEPEND on |
| 5 |
> sys-apps/sed, which is a system package (in profiles/base/packages) |
| 6 |
> since at least 2004. It boils down to some 2535 ebuilds, 1409 packages |
| 7 |
> and 14 eclasses, some requiring a version as high as 4.0.5, which went |
| 8 |
> stable in 2003. |
| 9 |
|
| 10 |
To follow up on that, some 496 ebuilds explicitly DEPEND on |
| 11 |
sys-apps/sed, with only a few apparently needing 4.1.5 and just the one |
| 12 |
seemingly requiring 4.2 (though it isn't obvious from the actual sed |
| 13 |
invocation). I haven't checked which of those RDEPEND on sys-apps/sed |
| 14 |
too, but it shouldn't be many. That means some two thousand acquire |
| 15 |
this DEPEND from an eclass, so for the majority of packages, this |
| 16 |
redundancy could be easily fixed, while the rest of them would probably |
| 17 |
keep inspiring developers new and old to keep introducing the dep or |
| 18 |
indeed be insecure about removing it. |
| 19 |
|
| 20 |
|
| 21 |
jer |
Archives