[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RFS: abcl

Darren Hoo <darren.hoo at gmail.com> writes:
> dget http://mentors.debian.net/debian/pool/main/a/abcl/abcl_0.23.1-2.dsc

lintian -IE --pedantic

P: abcl source: debian-control-has-unusual-field-spacing line 11
P: abcl source: debian-control-has-unusual-field-spacing line 27

    Extra spaces at the begining of the Depends Fields.
    Honestly, I don't care about these

I: abcl: arch-dep-package-has-big-usr-share 8187kB 99%
I: abcl-source: arch-dep-package-has-big-usr-share 4376kB 100%

    Any reason these packages are architecture specific? Both of them
    look like the same binary would work on any architecture.

I: abcl: hyphen-used-as-minus-sign usr/share/man/man1/abcl.1.gz:31
I: abcl: hyphen-used-as-minus-sign usr/share/man/man1/abcl.1.gz:32
I: abcl: hyphen-used-as-minus-sign usr/share/man/man1/abcl.1.gz:50

    Should be easy to fix, right? btw have you sent your manpage upstream?

I: abcl: package-contains-empty-directory usr/share/doc/abcl/examples/google-app-engine/src/META-INF/
I: abcl: package-contains-empty-directory usr/share/doc/abcl/examples/google-app-engine/war/WEB-INF/classes/META-INF/
I: abcl: package-contains-empty-directory usr/share/doc/abcl/examples/google-app-engine/war/WEB-INF/classes/abcl_ae/
I: abcl: package-contains-empty-directory usr/share/doc/abcl/examples/google-app-engine/war/WEB-INF/lib/
I: abcl: package-contains-empty-directory usr/share/doc/abcl/examples/google-app-engine/war/fasls/

    These look like it might actually right to keep it the way it
    already is.

W: abcl-source: extra-license-file usr/share/abcl-source/LICENSE

    Just delete that after dh_install -- the content is already in

Other notes

Looks quite well actually. Just the hint to abcl-source in abcl's
description looks a bit misplaced.

> I am wondering whether it is neccessary to integrate it with
> common-lisp-controller
> since abcl is running on JVM, it does not have the schemes like other  CL
> implementations that support  dumping core/image.

Maybe someone else can help here?



9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20110106/b3b6bae2/attachment.pgp>

Reply to: