[aur-general] community back-end rewrite
aaronmgriffin at gmail.com
Tue Dec 2 10:25:39 EST 2008
On Tue, Dec 2, 2008 at 5:38 AM, bardo <ilbardo at gmail.com> wrote:
> On Mon, Dec 1, 2008 at 9:22 PM, Daenyth Blank <daenyth+arch at gmail.com> wrote:
>> On Mon, Dec 1, 2008 at 14:46, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
>>> Hmm, perhaps we could just set a rule such that any removal at all is
>>> copied to the unsupported dir, and then people could simply delete the
>>> package from the front-end.
>> That makes a lot of good sense.
> Seconded. Unless we want repos to be more hierarchical, were a removal
> from core goes to extra, from extra to community, from community to
> unsupported. Somewhat impractical, imho.
> An alternative could be the implementation of a "move" abstraction.
> Then moving packages from any repo to any other (unsupported included)
> could be really simple and straightforward.
The official repos are handled much differently and DO have move
syntax. It's how we move things from testing to core. This is easy
because they are in the same svn repo.
But I don't thing we need to go overboard here. A system to move to
and from extra and community would be good. but it's not needed at the
More information about the aur-general