<div dir="ltr">Hello all,<br><br>Before I push libscout-clojure again I want to make a few questions:<br><br>Do we have to add a debian/VERSION tag? I see it in robert-hooke but not in slingshot.<br><br>Regarding the branches, I currently have master, upstream, and pristine-tar. According to <a href="http://wiki.debian.org/Java/JavaGit">http://wiki.debian.org/Java/JavaGit</a> this is enough but I see that slingshot and robert-hooke has them as remote branches. What am I missing?<br>
<br>debian/control source should be "scout", package name "libscout-clojure" git repository name "scout-clojure". Am I correct?<br><br>Cheers,<br>Eugenio</div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Thu, May 16, 2013 at 5:12 PM, Wolodja Wentland <span dir="ltr"><<a href="mailto:debian@babilen5.org" target="_blank">debian@babilen5.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, May 16, 2013 at 13:40 +0200, Eugenio Cano-Manuel Mendoza wrote:<br>
> If I'm not mistaken, Java libraries are distributed under the libXXX-java name.<br>
> I think it would be ideal to follow this convention for binary packages as<br>
> well, is clear enough to tell that a package is a binary clojure program by<br>
> just looking at the package name (libfoo-clojure). For source packages<br>
> UPSTREAMNAME-clojure looks sane enough (my opinion).<br>
<br>
</div>Yeah, exactly. I was not talking about binary packages at all. For those the<br>
libUPSTREAMNAME-clojure naming scheme is perfectly fine. I was just a bit<br>
confused to see git repositories of that name and would simply prefer iff:<br>
<br>
* git repositories have the same name as source packages<br>
* source packages use the upstream name, which we can suffix with -clojure<br>
if needed<br>
<div class="im"><br>
> Yesterday I tried to find out how exactly I'm supposed to use git for new<br>
> upstream packages. I was apparently doing things right except that I didn't<br>
> have pristine-tar enabled so git-import-orig didn't create the branch.<br>
<br>
</div><div class="im">> What do you do? Do you create the tar manually and import or clone and<br>
> create a branch for the debian patch?. I started to repackage scout properly<br>
> (I think), I'll keep you posted on that.<br>
<br>
</div>There are many packaging styles and it gets more and more complicated if you<br>
introduce version control systems into the mix. Lets forget about other VCS<br>
for now and concentrate on git. While it is true that one could, in theory, do<br>
everything in git and I would be interesting to learn a packaging style that<br>
makes use of this, but I adopted a packaging style that is essentially based<br>
on tarballs. I use git-import-orig to import the tarball, but forego the<br>
tedious act of having to create an actual tarball by using "git-import-orig<br>
--uscan" with a suitable debian/watch file. The result shouldn't be any<br>
different from cloning, calling "git archive .." and importing the tarball<br>
explicitly though.<br>
<br>
For this to work you, naturally, have to have pristine-tar enabled. I'll<br>
attach my ~/.gbp.conf to this mail which might provide some inspiration. As<br>
always I am not convinced that this packaging style is the best there is and<br>
will ever be, but so far I have been happy with it.<br>
<br>
I have to confess though that I *do* like packages such as awesome which uses<br>
a branch for upstream and one each for unstable, experimental, ... but I would<br>
have to spend some time on investigating this packaging style. Maybe Paul or<br>
Gergely have any more insoghts into this or even are opinionated about a<br>
particular style as well.<br>
<div class="HOEnZb"><div class="h5">--<br>
Wolodja <<a href="mailto:debian@babilen5.org">debian@babilen5.org</a>><br>
<br>
4096R/CAF14EFC<br>
081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC<br>
</div></div><br>_______________________________________________<br>
Pkg-clojure-maintainers mailing list<br>
<a href="mailto:Pkg-clojure-maintainers@lists.alioth.debian.org">Pkg-clojure-maintainers@lists.alioth.debian.org</a><br>
<a href="https://lists.alioth.debian.org/mailman/listinfo/pkg-clojure-maintainers" target="_blank">https://lists.alioth.debian.org/mailman/listinfo/pkg-clojure-maintainers</a><br>
<br></blockquote></div><br></div>