Am Sonntag, den 19.10.2008, 16:29 +0200 schrieb Bernhard R. Link: > * Daniel Leidert <[EMAIL PROTECTED]> [081017 13:08]: > > This is probably related to this report, so I simply attach it. If you > > think, this should be a separate report, please fell free to clone it or > > tell me, then I will clone it. > > > > I would like to copy a (source-)ackage from one component in a suite > > into a different component in another suite. But using the -C switch > > makes the command fail silently. The situation is pretty easy: I have a > > keyring package. For Debian I put it into "main", but for Ubuntu I would > > like to put it into "universe". So I tried: > > > > reprepro [..] -C universe copysrc hardy sid wgdd-archive-keyring > > > > but it "fails". I guess this is because -C defines the source component? > > Maybe you could add a switch or a syntax (copysrc hardy/universe sid) to > > allow this? Or is this a bad idea? > > Putting things from one component to another via pull or copy* > primitives is currently not supported (it would need logic to copy > around the files, which is not currently there, and some more way to specify > from which compontents to which components to copy stuff).
ACK. > The current description in the manpage (in CVS) is: > > | .B copysrc \fIdestination-codename\fP \fIsource-codename\fP > \fIsource-package\fP \fR[\fP\fIversions\fP\fR]\fP IMO this is ok. BTW: `\fP' AFAIK is pretty much the same as `\fR' now. If you want to change back to the previous font, then you need to use `\f[]' (as far as I understand the groff manual). > Do you think that makes it reasonably clear one cannot copy from one > component to another? Or could that need some improvements? IMO I misunderstood the -C/--component option. It says: > Specify a component to force into, to remove from or to list only. So I thought, in case of `copysrc' I can use it to "force into". But that's not the case. Instead it seems to be used as "only from" for `copysrc'. But I think, it is hard to document the special context of -C in the different cases. Maybe some other guy has a good suggestion how to do this. Maybe you can classify the options and say: [..] to force into (for foo class commands), to remove from (for bar class commands), ... [..] (like `find' divides its switches into different classes). Not sure. Grüße, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
