On Fri, 2005-07-22 at 12:35 -0400, Jeff Spaleta wrote: > The only users you really are going to help by exposing a full gui for > creating a repo definition file are those users who are already know > enough about which repos they want to actually edit a repo config by > hand anyways. A mechanism to make it easy for users to click on a > link on the 3rd party repo website to download and install the > provided reponame-release.. serves all users. Users of a repo should > be encouraged to use a repo config provided and updatable by the repo > maintainer instead of making one by hand. Instead of a package, could repos make their details available via RSS feeds? You would past an RSS URL into the GUI tool and it would pull down the latest details. If the repo maintainer needed to update something, they wouldn't have to roll and release a new package. The GUI could check for repo updates daily, weekly, whatever. Yeah, I know, time to take this part of the conversation to f-devel-l. If anyone likes my idea, feel free to take it and champion it. :) - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- Fedora-marketing-list mailing list Fedora-marketing-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-marketing-list
