[3dprinter-general] 3D-printer packaging

Thu Jan 23 18:45:45 UTC 2014

* Bas Wijnen <wijnen at debian.org> [2014-01-23 00:08:42 +0100]:

> Greetings everyone,
> 
> We just got a new request from Elena to join.  Welcome to the team. :-)
> 
> When I started the Alioth project, the server was having some trouble
> and I was unable to properly set everything up.  Then I got distracted,
> but I'm getting back to it now.  I would like to have a discussion on
> how we want to organize our work.

Thanks a lot for starting this!

> To record the state of this discussion, I started
> https://wiki.debian.org/3D-printer
> Please edit it with anything that should be there.
> 
> But first things first:
> I made Nicholas and Zlatan project admins, but they are not on this
> mailing list (I added both of you to bcc for this mail).  Please
> subscribe on [1] so you can follow the rest of this and future
> discussions.

Subscribed.

> Second, Nicholas is on the project twice (once as dd, once as guest).
> Can you remove your own guest user from there?

I asked for removal of my -guest account, but apparently that takes a while.
I've removed myself from the project (once :p).

> [...]
> 
> Also, if you feel like picking up a package, but it has an ITP by any
> team member, please ping the list to ask if you can go ahead and package
> it.  I'm sure the answer will be yes. :-)

Sure. I ITP'd printrun and I'd be glad for someone to take it over. Just add me
in Uploaders.

> Also, when filing new ITPs, please mention that it'll be maintained by
> the team.  Then team members know for sure that it's fine if they pick
> it up.
> 
> As for the maintainer and uploader fields in the packages:
> The Maintainer field should be set to this list:
> 3-D printer team <3dprinter-general at lists.alioth.debian.org>
> Policy says:
> > if the Maintainer control field names a group of people and a shared
> > email address, the Uploaders field must be present and must contain at
> > least one human with their personal email address.
> 
> This is obviously the case for us.  So when to add yourself to the
> Uploaders field of a package?  If you intend to care for it.  If you're
> just doing an upload to fix a bug and don't want to worry about the
> package any further, just mark it as a Team Upload in the changelog
> instead.

*nod*

> So far these are just formalities.  Now on to the first point of actual
> discussion.
> 
> How do we organize our repository?  I have limited experience with
> git-buildpackage, and I don't like it.  It's too hard to set up, and
> that scares potential contributers away.  So either we write a very
> short and simple list of instructions on the wiki, or we don't use it.
> Did I mention you should say so if you disagree with me? ;-)

I disagree with you :-) git-buildpackage enforces a branch structure, allows
you to integrate upstream tarballs in your repository, etc. As we have "young"
upstreams, I think we'll have to handle our share of tarball repacking, and
being able to use pristine-tar will be valuable.

I can write the list of instructions on the wiki.

> My suggestion for the repository is to use a directory for each package,
> which has the name of that package, including the upstream version (so
> it's ready to be used as a build directory).

You can build a package in any directory, AFAICT. The "upstream version" part
is just asking for pain at every package update. Plus, cool URIs don't change.

> In there, there is a debian/ directory which contains all our work.  We use
> source/format 3.0 (quilt) for all packages.

> To build a package, you'll need to get the tarball, either the new
> upstream version, or the orig.gz from the Debian archive.  It should be
> unpacked into the target directory and you're ready to run debuild.
> 
> When packaging a new upstream version, the tree should be moved to the
> new version number.  If the old version need to stay around for updates
> to stable or whatever reason, it can be copied instead.
> 
> How does that sound?

That sounds like a mix of CPOLD and real versioning: I don't like it at all.
The standard for git packaging is using the source name as the toplevel
directory, period. If you need to branch off an old version, you just do that,
using the name of the distribution you're targetting (wheezy, wheezy-backports,
experimental, ...).

> Then I have another point of discussion, but I'll start a new thread for
> that.
> 
> I think that's all for now.  I hope you all feel like getting this thing
> going, because the packages can certainly use some attention.

*nod*

Cheers,
-- 
Nicolas Dandrimont

"All language designers are arrogant.  Goes with the territory..."
(By Larry Wall)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/3dprinter-general/attachments/20140123/5d0e7066/attachment.sig>