Re: What is the process for creating/uploading new packages?
2010/12/22 Joachim Breitner <firstname.lastname@example.org>:
> Hi Eugene,
> Am Dienstag, den 21.12.2010, 20:00 +0300 schrieb Eugene Kirpichov:
>> 2010/12/21 Joachim Breitner <email@example.com>:
>> > Am Dienstag, den 21.12.2010, 16:32 +0300 schrieb Eugene Kirpichov:
>> >> 2010/12/21 Joachim Breitner <firstname.lastname@example.org>:
>> >> > In the former case, you should tell us what software it is and kindly
>> >> > ask, and we (the Debian Haskell Group) will probably maintain the
>> >> > package for you.
>> >> Yes, it is the "former" case - I want my package to be installable in,
>> >> say, Ubuntu, by sudo apt-get install mypackage.
>> >> I'm refering to these two applications:
>> >> http://hackage.haskell.org/package/timeplot and
>> >> http://hackage.haskell.org/package/splot
>> >> I'd happily do the package maintenance myself if that could speed up
>> >> the process, but I just need to know what to do :)
>> > ah, I see these are binaries, not Haskell libraries. The main focus of
>> > the DHG is libraries (these benefit most from a streamlined, consistent
>> > packaging) and with executables, there is more special work to do –
>> > ensuring that manpages exist, answering user’s bug reports and so on.
>> > Therefore, I’d like to see such a package to have a proper maintainer
>> > that feels responsible for such issues. He is still welcome to use the
>> > DHG infrastructure (as Trent is doing with Darcs). Anyone in the DHG
>> > interested in taking over the two *plot programs? These are nice
>> > programs, and we should have them!
>> I myself would be OK with doing all the maintenance for these
>> packages, if only I knew how it is done :)
>> (at the moment, I'm struggling to build a package and upload it to my
>> first-ever PPA on launchpad)
> Note that maintaining Debian packages is a bit more work than creating a
> Cabal package, because of all the processes around it and guidelines and
> stuff. If that sounds more interesting than scary: You are welcome!
Scary but I see no other way to give my apps any serious adoption
outside the haskell community :)
> A good start may be the packaging of other haskell programs, e.g.
> http://darcs.debian.org/pkg-haskell/bluetile/ or
> http://darcs.debian.org/pkg-haskell/alex/ or, well, pick any from
> These repositories contain just the Debian repository of the packaging,
> so extract it in your source directory.
Yeah, I've already based my package on this. Is it supposed to build
with a single "debuild (no arguments)" command? Didn't work for me
(will ask more questions tomorrow), I had to do "debuild -T
install/timeplot" and alike (which of course didn't work because of
all the unpackaged dependencies)
>> > There are also quite a number of dependencies not in Debian yet, which
>> > would have to be packaged.
>> Do you mean and we must have all haskell dependencies of the packages
>> also packaged? Is it because the package has to be buildable from
>> source, or is that also necessary for binary builds?
> Both: All our package have to be buildable using stuff in Debian by our
> users; and because we auto-build packages for many architectures (and
> for other reasons, such as security support), they need to be buildable
> by our auto-builders. So yes, each and every dependency has to be
> packaged in Debian.
> It’d be a help already if you could identify the set of packages
> required, but not yet in Debian. On
> you can see which packages are in Debian already.
OK, I see.
What if I have packaged a new library - how do I upload it? Am I
required to use the debian.haskell.org darcs repo, etc?
Also, I didn't quite understand what's up with the "source/format =
3.0 (quilt)" stuff - debuilds didn't work with it, complaining about
absence of an .orig.tar file, I had to change to 3.0 (native) and
ignore some warnings..
Generally, if I upload my "debianization" of a package somewhere, is
it reasonable to expect that someone will criticize and correct me? :)
(Thanks for all the help so far; once I learn, I'll help others :) )
> Joachim "nomeata" Breitner
> Debian Developer
> email@example.com | ICQ# 74513189 | GPG-Keyid: 4743206C
> JID: firstname.lastname@example.org | http://people.debian.org/~nomeata
Senior Software Engineer,
Grid Dynamics http://www.griddynamics.com/