You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Zied ABID (JIRA)" <ji...@apache.org> on 2011/03/13 12:12:59 UTC
[jira] Issue Comment Edited: (DERBY-5125) Derby 10.7.1.1 : Build
fails with javacc 5 (for Debian packaging)
[ https://issues.apache.org/jira/browse/DERBY-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006170#comment-13006170 ]
Zied ABID edited comment on DERBY-5125 at 3/13/11 11:12 AM:
------------------------------------------------------------
Hi Rick,
First thanks for your quickly reply. I'll try to answer your questions:
To have a free software in Debian, it must be compatible with Debian
Policy[1] [2]. Derby has already the License criteria (Apache 2).
After that, for soft coming with dependency or building dependency,
Debian Policy says that we must have this library already packaged into Debian which
guarantees at least three thinks :
First, no redundant libs everywhere in the system, so it's only one lib (package) for all soft that need it.
Second, it provide to any one that use Debian the package's source including dependency with just
a simple command line (apt source PACKAGE_NAME) to study it, modify
it etc. (FOSS). In addition that's let sources origin clear and verifying License (and
Debian Policy) easier.
Concerning Ubuntu, I say just that Ubuntu packagers haven't constrain as Debian Policy, so they
can add embedded libs on Uubntu packages (even if there is more and more voices claims to follow
some Debian Policy rules..) In addition I didn't find derby on Ubuntu packages [3]
(unless if you talk about javadb which is on multiverse repo as Software restricted by copyright
or legal issues) and packaging it to Debian imply generally that it will be available in future Ubuntu versions.
That's why I'm wondering if it's possible to use javacc 5.0 (by changing option in .jj files,
adding specific option to compiler, etc. ). It will help me a lot because javacc 5 is already
available in Debian (with all other lib that deby build depend on) and it will be mush easier
to change some lignes on derby source than packaging other version of javacc.
But if it's not possible, or there is a particular reason that let derby must be compiled with
javacc 4. I'll accept it and I'll try to ask javacc debian packager to provide it.
It's not in my mind, at any time, to advice derby developers to change javacc rev.
I'm ready to any collaboration to find a solution/workaround and to see derby in Debian.
Zied
PS: If you think that this bug in not a one, and this discussion should to be at dev mailing
list instead of but tracker, please accept my apologies, because I'm new in contributing world.
[1] http://www.debian.org/doc/debian-policy/
[2] http://www.debian.org/doc/packaging-manuals/java-policy/
[3] http://packages.ubuntu.com/
was (Author: zied):
Hi Rick,
First thanks for your quickly reply. I'll try to answer your questions:
To have a free software in Debian, it must be compatible with Debian
Policy. Derby has already the License criteria (Apache 2).
After that, for soft coming with dependency or building dependency,
Debian Policy says that we must have this library packaged already into Debian which
guarantees at least three thinks :
First, no redundant libs everywhere in the system, so it's only one lib (package) for all soft that need it.
Second, it provide any one that use Debian the package's source including dependency with just
a simple command line (apt source PACKAGE_NAME) to study it, modify
it etc. (FOSS). In addition that's let sources origin clear and verifying License (and
Debian Policy) easier.
Concerning Ubuntu, I say just that Ubuntu packagers haven't constrain as Debian Policy, so they
can add embedded libs on Uubntu packages (even if there is more and more voices claims to follow
some Debian Policy rules..) In addition I didn't find derby on Ubuntu packages [1]
(unless if you talk about javadb which is on multiverse repo as Software restricted by copyright
or legal issues) and packaging it to Debian imply generally that it will be available in future Ubuntu versions.
That's why I'm wondering if it's possible to use javacc 5.0 (by changing option in .jj files,
adding specific option to compiler, etc. ). It will help me a lot because javacc 5 is already
available in Debian (with all other lib that deby build depend on) and it will be mush easier
to change some lignes on derby source than packaging other version of javacc.
But if it's not possible, or there is a particular reason that let derby must be compiled with
javacc 4. I'll accept it and I'll try to ask javacc debian packager to provide it.
It's not in my mind, at any time, to advice derby developers to change javacc rev.
I'm ready to any collaboration to find a solution/workaround and to see derby in Debian.
Zied
PS: If you think that this bug in not a one, and this discussion should to be at dev mailing
list instead of but tracker, please accept my apologies, because I'm new in contributing world.
[1] http://packages.ubuntu.com/
> Derby 10.7.1.1 : Build fails with javacc 5 (for Debian packaging)
> -----------------------------------------------------------------
>
> Key: DERBY-5125
> URL: https://issues.apache.org/jira/browse/DERBY-5125
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.7.1.1
> Environment: Debian Linux Linux inf-7590.int-evry.fr 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 GNU/Linux
> java -version (also tested with sun jvm)
> java version "1.6.0_18"
> OpenJDK Runtime Environment (IcedTea6 1.8.7) (6b18-1.8.7-2)
> OpenJDK 64-Bit Server VM (build 16.0-b13, mixed mode)
> ant -version
> Apache Ant version 1.8.0 compiled on March 11 2010
> Reporter: Zied ABID
> Priority: Blocker
> Labels: build, libtool
> Fix For: 10.7.1.1, 10.7.1.3, 10.8.0.0, 11.0.0.0
>
>
> I try to and Apache derby into Debian, so I begin to compile derby
> sources [1], derby sources provide each own libs and javacc is one of
> them. In Debian, javacc version is 5.0 [2].
> After some tries, I'm in a this situation : compilation success with the
> official [3] javacc 4.0 and fail with the 5.0 official one.
> I think that is related with javacc options passed in .jj files
> (ex. java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj lines 2-14)
> I don't know much about javacc, so I can't resolve unless modifying
> options blindly and I'm afraid that isn't enough ...
> Best regards,
> Zied
> [1] http://svn.apache.org/repos/asf/db/derby/code/tags/10.7.1.1/
> [2] http://packages.debian.org/squeeze/javacc
> [3] http://java.net/projects/javacc/downloads
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira