Re: Cutting a gnustep-gui release

[Ivan Vučica]

0.25.1 will not include the wayland backend.

On Tue, Apr 4, 2017 at 8:15 AM, Gürkan Myczko <address@hidden> wrote:

will it have the -wayland back? clang? yay !!!!

:) thumbs up

Gürkan
Tel. 076 436 72 00

> On Apr 4, 2017, at 06:03, Eric Heintzmann <address@hidden> wrote:
>
> Hi,
>
> ( Debian is currently frozen, so new gnustep packages won't be included
> in Debian 9.
> But of course I will package it in experimental section)
>
> What I do at each release of gnustep-gui/back:
>
> 0   install all dev dependencies with apt (gnustep-base-dev &
> build-essential & all -dev packages needed).
>
> 1 -  rebuild gnustep-gui/back and see if all GNUstep apps still work
> fine without rebuild them
>
> 2 - rebuild all GNUstep  apps with the new gnustep-gui/dev, and see if
> they still build fine.
>
> 3 - repackage the new gnustep-gui/back, and see if debbuild show an
> ABI/API breakage when building.
> (to repackage I just have to copy the debian subdir into your source
> tree checked out from GNUstep's Subversion,
> and run debuild --
> https://www.debian.org/doc/manuals/maint-guide/build.html#debuild).
>
> 4 - run lintian
> (https://www.debian.org/doc/manuals/maint-guide/checkit.html#lintians)
> on the new gui/back packages .
> (I use lintian -i -I -E --show-overrides)
>
> Thanks
>
>> Le 04/04/2017 à 02:23, Ivan Vučica a écrit :
>>
>> It's not totally clear to me how to make a good use of this.
>>
>> Let's assume I have an existing .deb obtained via packages.debian.org
>> <http://packages.debian.org> (or an .so from that .deb), and I have a
>> source tree checked out from GNUstep's Subversion. Let's assume I have
>> no 'package tree' (i.e. one with debian/ directory) at a particular time.
>>
>> What would you like me to do to prepare the source tree (do I need to
>> obtain the debian/ directory, for example), and what would you like me
>> to execute in order to validate that the ABI didn't break?
>>
>> Thanks!
>>
>> On Tue, Dec 20, 2016 at 5:44 PM, Eric Heintzmann
>> <address@hidden <mailto:address@hiddenfr>> wrote:
>>
>>
>>
>>>    Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
>>>
>>> On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
>>> <address@hidden <mailto:address@hiddenfr>
>>    <mailto:address@hiddenfr <mailto:address@hiddenfr>>>
>>    wrote:
>>>
>>>    Debian Stretch will be fully frozen on 2017-02-05.
>>>    A special release before this date, with all you want to see in
>>>    the next
>>>    debian stable distro, would be a good idea.
>>>
>>>    (The current status of Stretch is "transition freeze", it means
>>>    that all
>>>    ABI/API breakage will be refused by the official Debian
>>    release team)
>>>
>>>
>>> Unless I missed something significant, the API/ABI should be
>>    backwards
>>> compatible. (I'd go through the list of changes before the release.)
>>>
>>> Any easy way to test whether Debian will consider API/ABI
>>    breakage has
>>> happened, which we could then add to the release docs?
>>>
>>
>>    https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates
>>    <https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates>
>>
>>    https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi
>>    <https://www.netfort.gr.jp/%7Edancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi>
>>
>>
>
>