Issue tracker moved to https://gitlab.archlinux.org/archlinux/aurweb/-/issues
FS#2888 - Package Screening System
Attached to Project:
AUR web interface
Opened by Simo Leone (neotuli) - Monday, 27 June 2005, 19:30 GMT
Last edited by Simo Leone (neotuli) - Friday, 01 July 2005, 22:32 GMT
Opened by Simo Leone (neotuli) - Monday, 27 June 2005, 19:30 GMT
Last edited by Simo Leone (neotuli) - Friday, 01 July 2005, 22:32 GMT
|
DetailsThis task is a reminder about a possible package screening system where all packages are marked "unchecked" as they enter unsupported, or are updated. After a TU checks over the package (perhaps doing a non-committed test build) they can mark it "clean", or advise the contributor as the the problems with their package.
|
This task depends upon
Closed by Paul Mattal (paul)
Friday, 29 July 2005, 12:33 GMT
Reason for closing: Implemented
Additional comments about closing: Applied the v2 patch along with turning package names green in list when they're safe.
Friday, 29 July 2005, 12:33 GMT
Reason for closing: Implemented
Additional comments about closing: Applied the v2 patch along with turning package names green in list when they're safe.
aur-flagsafe.diff
I know at the meeting we discussed this, IMHO we should do a quick and dirty implementation for 1.X (which I'm going to assume your patch does..since I haven't read it yet), see how it works out, make ajustments and "do it right" (tm) for 2.X .
For that reason, I'm also modifying this to be due for 2.0, although we'll certainly be messing with it before then.
EDIT: one more thing, maybe we should talk to the TUs before slapping this into effect, I'd like to get a feel for what they thing as a whole.
I have added a new item to the agenda for the next meeting regarding this.
PS. I forgot to include this:
ALTER TABLE Packages ADD Safe TINYINT(3) UNSIGNED DEFAULT 0;
ALTER TABLE Packages ADD INDEX(Safe);