fuel-dev team mailing list archive

[Dmitry Borodaenko <dborodaenko@xxxxxxxxxxxx>]

Considering that our workflow is strongly centered on Git, I think
git-buildpackage might be the best match. Ever since Debian Ruby
Extras team migrated to git-buildpackage, I've been using it for all
my Debian packaging with great satisfaction.

http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
https://wiki.debian.org/Teams/Ruby/Packaging#Using_Git

Debian Packaging slides I've made back in 2012 have a summarized
description of the whole workflow in Russian (with slight bias towards
Ruby but most of it is equally applicable to Python based and other
packages):

http://people.debian.org/~angdraug/debian-packaging-2012.pdf

It can also be used to build RPM packages:

http://marquiz.github.io/git-buildpackage-rpm/gbp.rpm.intro.html

-DmitryB

On Jan 8, 2014 7:17 PM, "Roman Alekseenkov" <ralekseenkov@xxxxxxxxxxxx> wrote:
>
> Thanks, Jay.
>
> Mike, Roman V.,
>
> Is Quilt something that we can use? E.g. internally when we apply patches in OSCI on the top of upstream OpenStack code.
>
> Thanks,
> Roman
>
> On Tuesday, January 7, 2014, Jay Pipes wrote:
>>
>> Here you go :)
>>
>> Quilt: http://savannah.nongnu.org/projects/quilt
>>
>> Guilt was a Git-specific Quilt clone (Quilt is agnostic to the source
>> control system), but it looks like the developer of Guilt is no longer
>> maintaining the source :(
>>
>> Here is also a good article on using quilt to managege patches, but it's
>> Debian specific:
>>
>> http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
>>
>> Best,
>> -jay
>>
>>
>>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>