[aur-general] Vote - Moving [community] to use same system as main repos

Angel Velásquez angvp at archlinux.com.ve
Mon Jan 26 08:16:42 EST 2009

On Tue, Jan 27, 2009 at 1:10 AM, Abhishek Dasgupta <abhidg at gmail.com> wrote:
> 2009/1/26 Angel Velásquez <angvp at archlinux.com.ve>:
>> 2.- The accounts on AUR, Forums, Wiki, Bug tracker should be unique, I
>> mean, I have differents accounts with the same login and different
>> passwords, in differents parts of the portals,
> I've no idea how this might be possible. It'd be nice, but punbb,
> flyspray are all separate packages...

I know that punbb and flyspray and mediawiki are separate packages,
but it's not impossible, in the place that I've worked before we used
an LDAP backend to handle the accounts, so the database of the users
will be the same, it's a thing to develop (if isn't developed yet) the
autentication routines for these packages against LDAP.

>> 4.- Every package's page should have links with a text like "bugs
>> related to this package" (and the list of the bugs of this packages,
>> to avoid to readding new bugs) and also a link "add new bug for this
>> package" these links will call directly the bugtracker, the button
>> about flag out of date should be considered to add a bug report? i
>> don't like the idea, but it will be good if a new version of a package
>> solves old bugs...
> bugs.archlinux.org does not have a "Package" field for its bugs, so we'd
> have to search the bug titles. Something like this:
> [Show bugs for pitivi](http://bugs.archlinux.org/?string=pitivi&project=4)
> --
> Abhishek

As I said, we will have to develop patches to realize these ideas,
isn't easy, but isn't hard at all, adding fields on the database,
something like package_id, or modifying the form where the bug is
added forcing to add the package name should be a way to do it.

Then we can develop a script with the result of this query
http://bugs.archlinux.org/?string=pitivi&project=4 in a format more
flexible like XML, so we can read this XML and add it a cool list on
the page handling it with JavaScript (a.k.a AJAX), this isn't hard to
do too (I worked with this before too).

The hard thing is install these backends and migrate the old stuff to
the new plataform, so I will understand if this doesn't like to much
to the people.

Thanks for your time

Angel Velásquez
angvp @ irc.freenode.net
Linux Counter: #359909
Arch Linux Trusted User

More information about the aur-general mailing list