Also, note that for cl-asdf, I'm currently not using the git repo on
alioth (that is slowly bitrotting), but directly the upstream git
repo, with tag RELEASE and branch release being used as respective
upstream and debian trees in make targets.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
A man is usually more careful of his money than he is of his principles.
                — Edgar Watson Howe




On 19 August 2010 15:09, Faré <fah...@gmail.com> wrote:
> On 19 August 2010 04:41, Milan Zamazal <p...@zamazal.org> wrote:
>>>>>>> "F" == Faré  <fah...@gmail.com> writes:
>>
>>    F> Note that if you already uploaded anything to any official repo,
>>
>> Not yet.
>>
>>    F> LICENSE is created by the Makefile, and I don't know the correct
>>    F> way to tell git-buildpackage to ignore it.
>>
>> Isn't it possible to remove it in `clean' target?
>>
> Looks like it works. See the new tentative cl-asdf 2.005 in mentors.
>
> And right *after* I release 2.005, a surge of activity results in new
> bugs being filed and fixed. Expect a 2.006 soon. Sorry.
>
> [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
> The Slogan of "Language Independence" is often but the pride that 
> self-ignorant
> monolinguists put in not calling "language" the collection of barkings and
> grunts they invent to interact with their computers.
>

_______________________________________________
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel

Reply via email to