Falcon

it should be easy to copy packages between pockets

Bug #261193 reported by Dennis Kaarsemaker
6
Affects Status Importance Assigned to Milestone
Falcon
New
Undecided
Unassigned

Bug Description

Basically, I want to have both unstable and stable pockets. I want the unstable pocket to be built automatically from our sources, but I don't want to manage a separate branch and force people to merge to the stable branch once it has been tested. I'd like to just copy the (now tested) package from one pocket to another.

It shouldn't need to be rebuilt, as I'm not building for another distribution. I'd rather save the man and machine cycles and just migrate the package as part of the testing process.

Can this be done with the Falcon shell? (It doesn't appear the documentation for the Falcon Shell is online right now.) Or do I need to add the feature myself?

Thanks!
Steven Black

Revision history for this message
Gunnar Thielebein (lorem-ipsum) wrote :

+1 for this feature

another approach would be to have metacomponents which will include other pockets components too. Question what is easier to implement?

Revision history for this message
Steven Black (blacks-indiana) wrote :

tekknokrat:

Wouldn't having metacomponents that automatically include other pocket components mean that, in my case, when I put something in the "unstable" pocket, it would automatically go to the "stable" pocket as well?

If so, then that is explicitly what I do *not* want. I don't want any automatic pocket migration, otherwise I invalidate the usefulness of having both a stable and an unstable pocket.

Cheers,
Steven Black

Revision history for this message
Gunnar Thielebein (lorem-ipsum) wrote :

Steven Black:

yes you are right that would be of no use.
I was thinking about packages which are independent of distribution and which could be shared between all without copying.
Minor example would be the keyring package of a repository. That would fit lets say in a pocket "all" with component "main" and be wrapped by metacomponent "all".
I think its up to the admin to configure the repository wisely enough to not mix "stable" and "unstable".

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.