My vision for it:
Users enter a backport request into a web interface.
The request is quickly run through a set of rules (i.e. no libraries, package blacklist), and then a build is done.
After the build, users can "pick up" their debs. Other users with the same request will get the same debs (caching)
Administrators (i.e. Backports Team) can get an overall report of all
successful backports, along with most popular packages. Upon their
command, the package will enter the official Backports branch.
On 12/26/05, skora <keyshawn632@xxxxxxxxx
> wrote:Hi,
If I'm understanding the proposal correctly, could the project
include the feature for the end user to insert a package name into the
web form, and find out the status of the backport, and if it has not
been requested yet; it would be built on demand and submitted to the
servers (if it cannot be backported due to conflicts, a message would
be displayed).
Is this project aimed at the end user, or those with immediate experience who want to assist in building backports; or both ?
Thanks,
skora.
2005/12/26, John Dong <
jdong@xxxxxxxxxx>:
This would be a great idea, and thanks Martin for taking the
initiative. I `am having to deal with more and more duplicate requests
over at the forums...
--
ubuntu-backports mailing list
ubuntu-backports@xxxxxxxxxxxxxxxx
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
--
ubuntu-backports mailing list
ubuntu-backports@xxxxxxxxxxxxxxxx
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
|
