I've been thinking on submission (since i'm a novice packager, i have no good experience with this, so i ended up talking to my mentor on submission stuff).
So i was thinking: .spec files are used to tell the buildbot how to build and package an srpm. why don't we have a similar way to do submission? (or even include this in spec file?) the things is, i want something that should work in most, if not all cases, but still be simple. what would be interesting: * submission parameters: ie: where to put rpm (core, tainted, non-free) or nice to have: * make this also work multiple times, for packages that are submitted multiple times (think about tainted stuff, that is rebuilt with extra %define), and still have only one srpm. * bootstrapping options? some way to have %defines that disable some stuff for bootstrapping (or even cyclic builddependencies in certain pacakages) in short, the idea is to have: 1. X, that is simple, elegant and works for all cases 2. stuff happens 3. profit :-P or to make it easier on packagers (and possibly reduce errors in wrong submission), so that just "mgarepo submit <package>" would automagically work correctly. i think this idea would be usefull if it was not too complex, unfortunately i have no solid concrete ideas about this. but perhaps someone else has any good suggestions about this?