[Asdf-devel] Wanted: Debian packager

[Robert P. Goldman]

Faré wrote:
> Here's the patch I've committed on my local release branch, but
> haven't pushed to common-lisp.net yet, pending maintainer approval.

That's fine with me; you have my blessing.

Kambiz, if you'd like to take over, that would be a huge help. I don't
think I'm going to be able to maintain enough of a bleeding-edge install
to be packaging.

Contact me off list if you need support and/or access to the repo.

best,

r



> Note that
> 
> 1- the email listed at the end of the top entry of the changelog has
> to be the same as the person who's going to sign the package with his
> PGP key as registered on mentors.debian.net, before the package is
> uploaded. So if someone else is going to upload this or future
> packages, the address should be amended (and also added in the
> debian/control file).
> 
> 2- lintian ../cl-asdf*.changes is your friend.
> 
> 3- To create the package I'm using the version of the release script
> that's in master,
> 
> 4- A good exercise in further bootstrapping ASDF would be convert
> bin/asdf-builder to a trivial cl-launch script + a system asdf-build
> (or meta-asdf? whatever), and the Makefile to a trivial wrapper that
> invokes it (except for the initial bootstrap of the concatenated
> build/asdf.lisp), and the Makefile targets into as many secondary
> systems of asdf-build. I'm refraining from doing more of it, since I'm
> moving to new projects.
> 
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
> A single flaw in someone else's beliefs, they are discredited. Repeated
> obvious flaws in your own, you keep the blind faith. Government saves!
> 
> 
> On Fri, May 16, 2014 at 8:57 AM, Kambiz Darabi <darabi at m-creations.com> wrote:
>> Hello,
>>
>> On 2014-05-16 07:12 CEST, Faré <fahree at gmail.com> wrote:
>>
>>> That said, I can do the asdf debian package one last time for 3.1.2.
>>> I've experimented a bit and come up with a better recipe. Apparently
>>> the trick to avoid dealing with complications is to work in a branch
>>> where the only changes since the upstream release tag are in the
>>> debian/ directory. If you let me do it, I'll do it in the release
>>> branch. I updated the bin/asdf-builder script to do the release
>>> (moving code from the Makefile and making it better — scripting is SO
>>> much better in Lisp). Of course, the script as exists in the release
>>> branch is insufficient, and since it does a git clean -xfd we need to
>>> extract it from master under another name everytime.
>>> So: I committed some debian-only changes in my release branch (not
>>> pushed — but I can do it if you approve, and even upload), and ran:
>>>   git show master:bin/asdf-builder > bin/x && chmod a+x bin/x &&
>>> ./bin/x debian-package
>>> and it looks like it worked. I can push all that if you want, or show
>>> you how to do it. It's a matter of
>>>   git checkout release ; git show master:debian/changelog >
>>> debian/changelog ; edit debian/changelog
>> I have never packaged for Debian, but I use it since rex (1996). With a
>> bit of hand-holding, I might be able to do the packaging work.
>>
>> Where can I fetch your changes?
>>
>>
>> Kambiz Darabi