<div dir="ltr"><div>Hi,<br><br><br></div><div><div><div><div><div class="gmail_extra"><div class="gmail_quote">2013/10/28 Paul Boddie <span dir="ltr"><<a href="mailto:paul@boddie.org.uk" target="_blank">paul@boddie.org.uk</a>></span><br>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I was wondering which project we should be targeting. I see there are "3.1"<br>
and "Development" projects, and when I tried to build the "Development"<br>
packages myself there seemed to be some kind of fundamental (non-packaging-<br>
related) build issue, whereas the "3.1" packages didn't exhibit the same<br>
problems.<br>
<br>
If we're fine-tuning the packaging is it best to target "3.1" in order to not<br>
have to deal with two different variables at the same time, or should it be<br>
safe to target the "Development" stuff? Also, where do the "Updates" come into<br>
this?<br></blockquote><div><br></div><div>I am also confused by this. Which project should people willing to help with Debian packaging should work with? I am under impression that following a moving target (which I understand Kolab:Development project is) is flawed. I think that we should focus on getting 3.1 packages to shape and then port necessary changes to the development project.<br>
<br>I also have trouble to actually understand how Debian packages are being built here. Let's take the pykolab package:<br>
<br>pykolab$ ls -al<br>razem 392<br>drwxr-xr-x 3 matik matik 4096 paź 29 13:57 .<br>drwxr-xr-x 4 matik matik 4096 paź 29 13:57 ..<br>-rw-r--r-- 1 matik matik 10467 paź 29 13:57 debian.changelog<br>-rw-r--r-- 1 matik matik 3370 paź 29 13:57 debian.control<br>
-rw-r--r-- 1 matik matik 640 paź 29 13:57 debian.rules<br>-rw-r--r-- 1 matik matik 7094 paź 29 13:57 debian.tar.gz<br>drwxr-xr-x 2 matik matik 4096 paź 29 13:57 .osc<br>-rw-r--r-- 1 matik matik 333461 paź 29 13:57 pykolab-0.6.8.tar.gz<br>
-rw-r--r-- 1 matik matik 1086 paź 29 13:57 pykolab.dsc<br>-rw-r--r-- 1 matik matik 14742 paź 29 13:57 pykolab.spec<br><br></div><div>I understand that debian.tar.gz is the debian directory from the source package. This layout is quite different from what I am used to when working with debian packaging so I have some questions regarding this file:<br>
<br>
* Why is it a tar and not a proper directory?<br>* Why there are some files (debian.{changelog,control,rules}) separated from the debian.tar.gz?<br>* What connection does it have to git://<a href="http://git.kolab.org/git/pykolab" target="_blank">git.kolab.org/git/pykolab</a> referenced by pykolab.dsc? (in fact this URL seems to be broken)<br>
</div><div>* Does this have any connection to <a href="http://git.kolabsys.com/apt/pykolab/">http://git.kolabsys.com/apt/pykolab/</a> git repository?<br></div><div>* Is debian.tar.gz generated somehow? According to Timotheus' how-to [1] one should untar it, make changes to the files inside, tar it again and push for building. Are these changes kept in some kind of version control?<br>
<br><br></div><div>Also, some packages (e.g libkolab) seem to have patches inside them. I guess that they are needed for RPM generation from *.spec files. Is that true?<br></div><div><br></div><div>I am also wondering where the pykolab-0.6.8.tar.gz file is coming from. I guess that some of these questions are related to inner workings of OBS. I am willing to learn, but I have trouble to find relevant information. Could you point me to some information on how this is all set up and/or how building works in OBS? Some kind of build script might suffice, but I'm unsure where to look for it.<br>
<br></div><div>Regards,<br><br><br></div><div>Mateusz.<br></div><div><br>[1] <a href="http://kolab.org/blog/timotheus-pokorra/2013/10/24/howto-improve-debian-packages-using-obs">http://kolab.org/blog/timotheus-pokorra/2013/10/24/howto-improve-debian-packages-using-obs</a><br>
</div></div></div></div></div></div></div></div>