Simo's original commit text:
The idea of safe flagging is unclear, poorly named, misunderstood,
and not even used. At the time this patch was created, less than
a third of the packages in unsupported were flagged safe, and less
than a tenth of users knew how to interpret it.
The safe flag has been replaced by a disclaimer on the main page.
There is no need to check in dummy data if it is available by running the
script that sat right next to it in the repo. Doh!
Signed-off-by: Dan McGee <dan@archlinux.org>
This reverts commit 9b4472ef2fb91e91539def70f905cfe1ec6a8a3a.
We have decided to put the button by itself on the bottom, so
it does not get lost. This might be reconsidered in later UI
revamping.
try_login() to login users
valid_username() checks if a new username fits criteria
valid_user() checks if the user exists in the database
good_passwd() only checks for minimum password length for now.
can be later expanded to tell a user to make a stronger password.
valid_passwd() checks if the password for the specified user is correct
user_suspended() checks if the user is suspended (or not)
user_delete() deletes a user (it doesn't orphan PKGs yet though)
user_is_privileged() returns privilege level User (0) TU (2) Dev (3) of
user ID. 0 is used for a regular user for ease in conditionals.
Also: Enforce proper usernames on account creation or editing
Fix bug where $SUPPORTED_LANGS needs to be reset on account creation
Fix bug where an account could be created with an empty passwd
Display (required) beside password fields on account creation
Enforce good_passwd() on account creation
TUs and Devs can edit a user to have a username that doesn't conform to
the standard valid_username(). This is to allow them to edit old
accounts without messing up the user name.
Signed-off-by: Loui Chang <louipc.ist@gmail.com>
try_login() to login users
valid_username() checks if a new username fits criteria
valid_user() checks if the user exists in the database
good_passwd() only checks for minimum password length for now.
can be later expanded to tell a user to make a stronger password.
valid_passwd() checks if the password for the specified user is correct
user_suspended() checks if the user is suspended (or not)
user_delete() deletes a user
Also: Enforce proper usernames on account creation
Fix bug where $SUPPORTED_LANGS needs to be reset on account creation
Fix bug where an account could be created with an empty passwd
Display (required) beside password fields on account creation
Enforce good_passwd() on account creation
Signed-off-by: Loui Chang <louipc.ist@gmail.com>
This reverts commit 9b4472ef2fb91e91539def70f905cfe1ec6a8a3a.
We have decided to put the button by itself on the bottom, so
it does not get lost. This might be reconsidered in later UI
revamping.
Currently, locations include none/current/extra/unstable. Since no package should be located in such an area, there's no point in including them in search criteria. The proper way to do this might be to delete the SQL table data relating to this, but this will suffice for now.
Signed-off-by: tardo <tardo@nagi-fanboi.net>
The html/web/xml directory is where the RSS feed gets stored. This was not
in the release tree, but has now been added. It should be set up with
permissions that allow the webserver to write to it.
Rather than rely in any way on config.inc, which is expected to be edited
by the user and to persist across versions without change, the version
string definition is stored in version.inc and included from aur.inc.
Previously if the package was not in community or unsupported, the link didn't point anywhere. Now it uses http://archlinux.org/packages/search/$pkgname. If there's a better way, someone needs to let me know. As far as I know, there's no sure way to link directly to a package without knowing the pkgid.
Signed-off-by: tardo <tardo@nagi-fanboi.net>
