On 10/25/07, Jason Chu <[EMAIL PROTECTED]> wrote:
>
> (....)
> Not trying to push some sort of developer agenda here, but we've always
> tried to use the bug tracker for things like this. If the update is
> complicated, it's great to attach a PKGBUILD to a bug report and it also
> makes it very easy for people to see the state of a package update (and
> why
> its being held back).
>
> The eclipse package is a prime example. If there was a ticket, everyone
> could be refered to it and know the status of the eclipse package *and* be
> able to help with it.
>
> Jason
>
> _______________________________________________
> arch mailing list
> [email protected]
> http://archlinux.org/mailman/listinfo/arch
>
>
>
Nice idea. I really second that, yet I think some means to point the user to
the specific ticket in the package page is really welcome, as finding this
kind of stuff in bugtrackers tend to be hard IMHO. If dev comments are not
welcome, at least some kind of pointing to a specific ML-thread/forum
post/flyspray entry/etc would be nice.
--
Cheers,
Rodrigo
A computer is like air conditioning: it becomes useless when you open
windows.
~Linus Torvalds
_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch
