[csw-maintainers] Registering packages in mantis (was Re: [csw-pkgsubmissions] newpkgs firefox_l10n_af, ...)

[Dagobert Michelsen]

Hi Phil,

Am 23.02.2010 um 17:40 schrieb Philip Brown:
> On Tue, Feb 23, 2010 at 6:15 AM, Dagobert Michelsen  
> <dam at opencsw.org> wrote:
>> Am 23.02.2010 um 15:12 schrieb Philip Brown:
>>> not quite sure what you mean by "bundle" Dago... but seems to me  
>>> that
>>> in this case, the packages in question are pretty clearly a "part  
>>> of"
>>> firefox already
>>
>> The idea is to map packages to "bundles" and report bugs with the  
>> "report
>> bug" button on the packages page going to the Mantis project named  
>> after
>> the bundle. This reduses and unifies the buglisting. That means that
>>  CSWmypkg
>>  CSWmypkgdevel
>>  CSWmypkgrt
>>  CSWmypkg_i18_de
>> would all belong to the bundle "mypkg" derived after the main package
>> catalog name.
>
> Erm.. I'm not exactly sure what that would gain us.
> we would avoid the extra 60 (yes, 60!) extraneous firefox local
> packages being listed in mantis.

Yes. We would basically halve the number of listed items as all  
runtime and
devel packages would collapse to the base bundles also.

> But we would then have them in the output of
> http://www.opencsw.org/packages. and it would make things quite a bit
> more complex to maintain, web-code wise. and release-wise.

But it would gain "What packages belong to that software?" which is
now without browsing GAR to doable.

> [complexity: what mechanism would we use to derive the "main package"
> name, and where/how would this information be stored?]
>
> Seems simpler, and yet quite straightforward, to have an  
> understanding of,
>
> "If there is   softname, softname_FOO, softname_BAR, softname_BAZ, and
> there are not separate mantis categories,  you are expected to go file
> bugs for the base name 'softname' "

And pm_softname and py_softname?

> Even a newbie user should be able to figure that one out as-is.

It should not replace the package listing. It is an additional page
like /bundles/<bundle>/ which contains information about the package
in general (like how to use it) and links to the packages it contains.

The information should be quite easily optainable by just looking at the
upstream URL in the info field: same field - same bundle.


Best regards

   -- Dago