On Sonntag, 13. April 2008 01:13 gan lu wrote:
> Yes, the thing bothers me is that you see how many times a package has being
> flaged for quite a long time, but without any feedback from maintainer or
> devs, which is sad for you.
Yes, i don't like this feeling of knowing nothing too but on the other side i
can understand that a maintainer don't want to say that he/she have no time
to do this or to say even the same as at example that mainstream is broken
for reason xyz.
So i expand my idea to this layout with two standard answers and one field for
explanation. Example:
This package has been flagged out-of-date
[ ] I have no time at the moment
[ ] It depends on a package which is in testing
[X] Other reason: "The mainstream is broken because
it don't compiles with gcc 4.3"
I think this could have positive side effects:
- User who see that time is the problem make it by themselves if they need
this update in this moment.
- More users could decide to use testing for this case which could be better
too.
- More people than only the maintainer search (or create) a patch or contact
the authors of the mainstream.
But still again this is only a idea for an half-automatic interface of the
communication and not a wish for more officialism for the devs.
See you, Attila
