debian package and 0.39_beta thoughts

[Mildred Ki'Lya]

On 12/05/2009 08:53 PM, PICCA Frédéric-Emmanuel wrote:
> Hello,
>
> I started working on the debian package of the 0.39 version, but...
> what is this Makefile ?
>
> there is no way to produce a debian package with this Makefile,
> the installation process is interactive ????
>
> why the current Makefile from stable is not in this package ?
> It provides a dist target to produce the package, and the all target build
> in a non interactive mode the lisaac program, etc...
> If the current dist target is wrong it must be updated to generate the right .tar.gz
>
> there is also no tag corresponding to the "official" 0.39 beta version in the repository.
>
> could you add the tags in the repository and generate the .tar.gz using the right makefile
>
> that way it will ease a lot the packaging work.
>
> thanks.
>   
Hi,

Well, there was a lot of complains about the Makefile and that it should
by default run install_lisaac.li. There was also the problem that
shorter.c is no longer in the bin directory (at least in the repository)
and that was a problem with install_lisaac.

So, Ben (I suppose) decided to remove everything and only include stuff
for install_lisaac.

When I merged this specific part to the stable branch, I just kept most
of the old things in the makefile, while keeping the default behaviour
desired for install_lisaac. But of course this was never merged back in
the master branch and never appeared in the beta.

I suppose this will find its way in the next beta release.


Now, I think I created a tag: lisaac-0.39b

http://git.debian.org/?p=lisaac/compiler.git;a=shortlog;h=a23685f842d6d34a8da2e78e6ca04be22780ad33

> Debian part :)
>
> As I am using git-buildpackage to produce the debian package,
> I need three dedicated branch
>
> 'upstream' (equivalent of the current stable branch)
> 'debian'
> 'pristine-tar' for the pristine tar delta (this branch help to generate the tar.gz from the upstream branch)
>
> on the upstream branch there is tags for each package like this one upstream/0.13.1 etc..
> on the debian branch they lokks like debian/0.13.1-1 etc...
>
> so must we create thoses branches on the compiler.git repository.
> or must we create a dedicated repository for the debian packaging ?
>   

I think a dedicated repository, Creating a debian branch is fine I think
(even if that raised some questions here) but having that many branches
just for debian would create too much confusion.


Mildred

-- 
Mildred Ki'Lya
╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
│ Jabber, GoogleTalk: <mildred at jabber.fr>
│ Website: <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20091205/9c776336/attachment.pgp>