| 1 |
On Wed, Jan 20, 2016 at 12:34 PM, Mike Frysinger <vapier@g.o> wrote: |
| 2 |
> On 18 Jan 2016 00:57, Joshua Kinard wrote: |
| 3 |
>> On 01/17/2016 14:57, Michał Górny wrote: |
| 4 |
>> > sys-apps/kexec-tools : |
| 5 |
>> |
| 6 |
>> Better suited for base-system, maybe? |
| 7 |
>> |
| 8 |
>> > sys-fs/jfsutils : |
| 9 |
>> |
| 10 |
>> Definitely base-system, as xfsprogs is already maintained by them. |
| 11 |
> |
| 12 |
> sounds fine for both. generally fs tools probably should live under |
| 13 |
> base-system for consistency. |
| 14 |
|
| 15 |
Nothing wrong with consistency, but I'd prefer a package to be placed |
| 16 |
under the base-system project because the base-system project members |
| 17 |
intend to maintain it. I don't want to see packages placed into |
| 18 |
projects simply because they're similar to other packages in those |
| 19 |
projects if it means they'll just be neglected. |
| 20 |
|
| 21 |
I have no idea which is the case here. If the base-system maintainers |
| 22 |
want to maintain these two packages, have at it! If not, leave it as |
| 23 |
maintainer-needed. |
| 24 |
|
| 25 |
-- |
| 26 |
Rich |
Archives