Re: best policies for third party Debian packaging and get-orig-source target
I'm really happy that I asked back! ;-)
On Tue, Jul 30, 2013 at 08:03:19AM +0000, Faheem Mitha wrote:
> On Tue, 30 Jul 2013 09:01:43 +0200, Andreas Tille <firstname.lastname@example.org> wrote:
> > Hi Faheem,
> > On Mon, Jul 29, 2013 at 04:24:21PM +0530, Faheem Mitha wrote:
> >> I've got Debian packaging for a piece of software I've written. This
> >> software probably is too specialized to be part of Debian.
> > Could you please tell us what specialized software you have written.
> > You might simply like to post your Description field here to let others
> > know.
> Hi Andreas,
> Certainly, but I'm pretty sure this is of no general interest.
You can never be sure! Sometimes it is of specific interest ...
> It is
> accompanying software for a paper I've written. It is just an
> implementation of the methods I've developed. The package description
> itself is fairly useless (I should think about how to write it
> better), but I include the abstract of the paper below. This probably
> could also use some work.
> We describe and implement a method to predict new members of a DNA
> sequence motif family using Bayesian model selection. This method
> assumes a specific correlation structure on the set of sequences. We
> apply our method to test the prediction of DNA sequence motifs in a
> cross-validation setup for two datasets.
The mailing list archive shows that in 2008 you had contributed to the a
plink related thread - so you might know the Debian Med project. In
case you are unsure you might probably want to have a look at the list
of packages which definitely fall into your field on our web
sentinel. If you want to have your package inside Debian (which
includes a lot of advantages starting from QA means until finally get
your publication listed on our web sentinel) you should move this thread
to Debian Med mailing list and we could talk about details there. I
personally can not see any advantage for you to create private packages
if you can have publicly available ones.
> The software uses SQL (PostgreSQL), Python, R and C++, so it is a bit
> of a hotchpotch, and while a small package, it has a large number of
> dependencies. Unfortunately the R packages I use are not all in
> Debian, last I checked.
So why not changing at least the availablity of the preconditions?
Looking forward to help you solving your packaging problem in Debian Med