Re: [Kolab-devel] Kolab Development packages now requiring a package for composer

2015-05-13 15:18 GMT+02:00 Sergio Talens-Oliag <[email protected]>:

> El Wed, May 13, 2015 at 01:59:58PM +0200, Mateusz Kijowski va escriure:
> > 2015-05-13 8:20 GMT+02:00 Timotheus Pokorra <[email protected]>:
> > I think patch command is responsible for the newline (well, it's a binary
> > file, not sure how Debian manages those inside a source package)
>
> On the new debian package format (3.0) binary files are usually
> distributed on
> the PACKAGE_VERSION.debian.tar.zx archive.
>
> On previous versions (1.0) binary files were put inside the debian/
> directory
> in ascii format (i. e. uuencoded) to be able to include them inside the
> diff.gz file and the files were recovered by the debian/rules files when
> needed.
>

Aha! So it seems that the choice we have is either fixing debtransform to
generate the PACKAGE_VERSION.debian.tar.xz or we do a uuencode of
composer.phar and a uudecode it in debian/rules ?

Regards,


Mateusz.


> >From the developers-reference:
>
>
> https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#changed-binfiles
>
> Greetings,
>
>   Sergio.
>
> --
> Sergio Talens-Oliag <[email protected]>               <http://www.iti.es/>
> Key fingerprint = FF77 A16B 9D09 FC7B 6656 CFAD 261D E19A 578A 36F2
> _______________________________________________
> devel mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/devel
>

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel