"Maciej (Matchek) Bliziński" <mac...@opencsw.org> writes: > 2013/8/11 Peter FELECAN <pfele...@opencsw.org>: >> To come back to my proposition, in which part of the code is the >> association made, i.e. uploader becomes maintainer? Answering this >> question can simplify my life instead of wandering all the surface of >> the system. > > The starting point is here: > http://sourceforge.net/apps/trac/gar/browser/csw/mgar/gar/v2/gar.pkg.mk#L716 > > Every other bits of infrastructure read this pkginfo field.
This I know. What I wish is to inhibit this, when supplying --nmu to csw-upload-pkg for an existing package. Where is this code situated? > I want to ask this question. It might sound like a rhetorical one, but > it's not: it's one of the central questions to the discussion: > > Do you become the owner of the package because you are willing to take > on the owner's duties, or do you take on the owner's duties because > you've become the package owner? Neither when I'm doing a NMU. Now, let me ask a pragmatical question: what is the reason for which my proposition is not worthy of implementation? -- Peter _______________________________________________ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
