[maemo-developers] Maemo extras repository package uploader/maintainer verification?

From: Nathan Anderson nathan at andersonsplace.net
Date: Fri Jan 22 19:21:56 EET 2010
Jeremiah,

	Thanks -- I have no issues with dropping my name into the maintainer
field; I just didn't want to steal any credit from the "real" authors of
those things that I just repackaged.   I do know the language of everything
I've repackages; and could probably muddle my way through something I didn't
know. ;-)

	If the standard is that I take the maintainer field; I'll make sure
to update all my packages.   Thank you for the clarification!

	I do notice that the docs was for pre-fremantle, and somethings are
no longer used.  (i.e. maemo-select-menu-location and maemo-installer-utils
I believe are no longer used in fremantle).    Can you tell me if thumb and
vfp options are still valid or does the autobuilder now automatically use
them.

Nathan.

-----Original Message-----
From: maemo-developers-bounces at maemo.org
[mailto:maemo-developers-bounces at maemo.org] On Behalf Of Jeremiah Foster
Sent: Friday, January 22, 2010 10:40 AM
To: maemo-developers at maemo.org
Subject: Re: Maemo extras repository package uploader/maintainer
verification?


On Jan 22, 2010, at 5:17 PM, Nathan Anderson wrote:

> Ok, I think I must be confused; I was under the impression that you 
> leave the maintainer field alone if all you are doing it packaging it up
for the
> maemo platform.    I don't actually "maintain" any of the code for several
> of the projects that I have uploaded.  

You do however maintain the package. So if there are bugs it is your
responsibility to push the bugs upstream if they are in the code. This is
how the responsibility is divided in debian anyway, it is not explicitly
laid out for Maemo but I think it ought to be self-evident. 

>  All I've done is did the work to
> "package" it up.

In many cases the developer is also the packager, but when the packager is
different from the developer(s) then the packager has to take on a bit of
responsibility for at least packaging QA. Maintaing the code as well is
usually not required, but it is considered a good thing if at least you know
the programming language it is written in, etc.

> Am I supposed to put in the maintainer field my name, or leave it as 
> the original team that wrote it.  The only thing I change is the 
> changelog to show that the program was packaged by me.  (i.e. sword 
> library, kernel
> modules)

The changelog is a must, but changing the maintainer name in the
debian/control file is also a must, according to maemo packaging policy.
Here is the policy in pdf: WARNING PDF!  >>
https://maemo.org/forrest-images/pdf/maemo-policy.pdf 

Jeremiah

> 
> Nathan
> 
> 
> 
> -----Original Message-----
> From: maemo-developers-bounces at maemo.org
> [mailto:maemo-developers-bounces at maemo.org] On Behalf Of Simon 
> Pickering
> Sent: Friday, January 22, 2010 7:00 AM
> To: 'Jeremiah Foster'; maemo-developers at maemo.org
> Subject: RE: Maemo extras repository package uploader/maintainer 
> verification?
> 
> 
> 
>>> What checks there are in place to verify that the package uploader 
>>> and the package maintainer field (shown to people who install the
>>> packages) match?
> 
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
> 

_______________________________________________
maemo-developers mailing list
maemo-developers at maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

More information about the maemo-developers mailing list