osc mkpac project package

[mcepl]

Is your feature request related to a problem? Please describe.
Looking at https://youtu.be/EQ5NWsW_tjo is a bit embarrassing to see in the introductory course are users-to-be asked to edit an XML file. That’s just a bad UI right there (actually, it is even unnecessary in this case, because in the very next step they check out the package and project anyway, so they could just turn it around and use even the current osc mkpac, but that isn’t the point here).

Describe the solution you'd like
Add a two-argument call of osc mkpac like this:

osc mkpac project package

which would create a new package in the already existing project on OBS, e.g. osc mkpac home:mcepl foo would create a new package foo in the already existing home:mcepl project.

Actually, we can even add -H option, which would create a new package in the user’s home project, so it would be osc mkpac -H foo in this case, but the other option would allow different projects.

[dcermak]

-H is the global flag for http debug, so I'd suggest to skip that

[mcepl]

On Fri Feb 23, 2024 at 12:20 PM CET, Dan Čermák wrote: -H is the global flag for http debug, so I'd suggest to skip that

Right, so it could be `--home` then.

[dmach]

I remember me struggling with this when I wanted to setup my OBS instance for testing, so 👍

First of all, I need to finish couple more pull requests to move osc.core from ad-hoc XML manipulation to object wrappers.
The wrappers already allow editing XML, I was also thinking about extending the edit mode with adding comments with documentation strings and possibly also commented elements that are not yet used. It might be useful in cases like this.

[smithfarm]

👍 I hit this, too. As a long-time user of osc, I was surprised to see that mkpac does not understand PROJECT PACKAGE, but only PROJECT/PACKAGE.