Re: [AD] a5 ubuntu ppa

[Jon Rafkind <workmin@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I used your debian directory to test out the ppa's. They work on precise and up. Older distros fail on the debhelper(>=9) dependency.

I'm not thrilled about joining a debian-devel-games list just to discuss this so I will avoid it if possible.

About the debian/ directory. It specifies a lot of stuff specific to 5.0 like filenames with 5.0 in the name so it will be hard/annoying to have a 5.1 build as well. Also the control file lists non-dev packages with 5.0 in the name but dev packages with just '5'.

Package: liballegro5.0
Package: liballegro5-dev

I think the dev package should have a 5.0 in it as well so that when 5.2 comes out people can install either or. Also it would make supporting 5.1 easier because it would result in a liballegro5.1 and liballegro5.1-dev package.

https://launchpad.net/~allegro/+archive/5.0

On 11/28/2012 04:14 PM, Tobias Hansen wrote:
> Hi,
>
> for us it is best to have the packaging repo on the Debian servers where
> all Debian developers and all members of the Debian games team can push.
> You can either join the Debian games team [1] and maintain your PPA
> packaging in branches of our repository (actually, 5.1 would go into a
> separate repo) or clone our repository, so that
> we can pull each others commits if necessary. I would advice against
> maintaining the packaging in the Allegro repository, because commits to
> a packaging repository are usually of a different nature that upstream
> commits. I would keep an eye on a second packaging repo, but not on all
> the upstream commits. We can discuss packaging related questions on the
> debian-devel-games list [2].
>
> Best regards,
> Tobias
>
> [1] http://wiki.debian.org/Games/Development
> [2] https://lists.debian.org/debian-devel-games/
>
> Am 28.11.2012 23:27, schrieb Jon Rafkind:
>> Well I suppose its reasonable not to have a top-level debian/ directory
>> but we could put it in misc/ or something.
>>
>> On 11/28/2012 03:17 PM, Peter Wang wrote:
>>>
>>> Probably not. As I understand it, it can interfere with down stream or
>>> we'd need to leave it out of releases.
>>>
>>> http://wiki.debian.org/UpstreamGuide
>>>
>>> "Many upstream code sources tend to include a rough /debian directory
>>> among source files to ease bleeding-edge package compilation and
>>> installation on debian (and derived) systems; while this is a good
>>> effort, it would be better to leave it out of the final tarball as it
>>> can interfere with debian's own packaging effort. Keeping it only in
>>> your VCS repository is usually a much saner default."
>>>
>>> On 29 Nov 2012 06:56, "Jon Rafkind" <workmin@xxxxxxxxxx
>>> <mailto:workmin@xxxxxxxxxx>> wrote:
>>>
>>> I think we should publish an Ubuntu PPA for both 5.0 and 5.1
>>> packages. I just learned that 5.0.8 is packaged for ubuntu raring
>>> (12.10) but not for any other distro and 5.1 is not packaged. It
>>> is very easy to set up PPA's. gusnan from #allegro-dev already has
>>> a debian/ directory going. I make ppa packages for another system:
>>> https://launchpad.net/~plt <https://launchpad.net/%7Eplt>
>>>
>>> I think we should include gusnan's debian directory in our git
>>> tree. http://packages.ubunut.com/search?keywords=liballegro5
>>>
>>> Then its a simple matter of uploading a tarball to launchpad, for
>>> which I just created a group: https://launchpad.net/~allegro
>>> <https://launchpad.net/%7Eallegro>
>>>
>>> I can set this up. The only real question is whether its
>>> appropriate to include the debian tree directly in our git tree.
>>>
>>> ------------------------------------------------------------------------------
>>> Keep yourself connected to Go Parallel:
>>> INSIGHTS What's next for parallel hardware, programming and
>>> related areas?
>>> Interviews and blogs by thought leaders keep you ahead of the curve.
>>> http://goparallel.sourceforge.net
>>> --
>>> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Keep yourself connected to Go Parallel:
>>> INSIGHTS What's next for parallel hardware, programming and related areas?
>>> Interviews and blogs by thought leaders keep you ahead of the curve.
>>> http://goparallel.sourceforge.net
>>>
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Keep yourself connected to Go Parallel:
>> INSIGHTS What's next for parallel hardware, programming and related areas?
>> Interviews and blogs by thought leaders keep you ahead of the curve.
>> http://goparallel.sourceforge.net
>>
>>
>>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlC4IzcACgkQcrWKoYzLQVhe7ACglWA2kz9XYLat2G38We5I8UiA
bkAAn3y5907S+bD9BqTjq8ybRbB6L8HN
=zedO
-----END PGP SIGNATURE-----