[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Debian-med-packaging] Packaging by students



Hello Andreas, Olivier!

Well the main policy differences seem to me (I have two simple packages accepted so far):

* They do not support Debian Maintainer uploads, they do not use the DM-Upload-Allowed field, so getting a package uploaded involves a
particular procedure (you set it to unstable from UNRELEASED, then one of the DD team members has a look and either uploads or comments and sets
back to UNRELEASED).

* They use git exclusively.

* They are sensitive to lintian experimental, info and pedantic tags.

Indeed, it only makes sense to follow both their and our (Med) policy, and be sensitive to lintian tags.

I do not want to have all my students added to the Perl team as well. If the one that gets the NHGRI::Blastall can work with git, I think I will
ask to have him/her added to that team and then that pack can go there. It makes sense, because that is likely to be reused by others. The other
Perl modules are just components of PredictProtein, so I would have those at Debian Med.

Best regards,
Laszlo

On 29/06/12 18:19, Andreas Tille wrote:
> On Fri, Jun 29, 2012 at 05:41:34PM +0200, Olivier Sallou wrote:
>>
>> Le 6/29/12 4:46 PM, Laszlo Kajan a écrit :
>>>
>>> None of these modules are in CPAN (not even the very useful NHGRI::Blastall). All but one - NHGRI::Blastall - make sense only in the context of
>>> PredictProtein, really.
>> In this case, it could make sense to be in Debian Med in my opinion, but
>> you should care to follow Perl policies.
>> Of course, this is my opinion...
> 
> It sounds reasonable and I'd go that far to say: If there are any
> conflicts between Debian Med policy and Perl packaging group policy we
> should gain for fixing this.  Droping the Perl team a note about
> your attempt seems reasonable as well.
> 
> Kind regards
> 
>        Andreas.
> 


Reply to: