Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
dev-java/jdbc-mysql-3.0.17 ebuild non-free RDEPENDS?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
NightMonkey
Guru
Guru


Joined: 21 Mar 2003
Posts: 356
Location: Philadelphia, PA

PostPosted: Wed Jul 27, 2005 6:10 am    Post subject: dev-java/jdbc-mysql-3.0.17 ebuild non-free RDEPENDS? Reply with quote

Hi, all. The ebuild for dev-java/jdbc-mysql-3.0.17 (just released to x86) has new RDEPENDS for:

dev-java/jta
dev-java/jdbc2-stdext
dev-java/log4j

Unfortunately, the first two new required packages have fetch resrtiction turned on due to license requirements from Sun. However, nothing in the CHANGES file indicates that these are required. I'm not familliar enough with the internals of Connector/J (aka jdbc-mysql) to say for certain if this is not required. I'd prefer, however, to not install these unless it is truly required for basic functionality.

Can someone who knows more than me chime in as to whether this is truly required? I've been using 3.0.16 witout these additions and have had no problmes with database connectivity.

Perhaps there's something I've missed, so here's the CHANGES file excerpt for 3.0.17:

Code:
06-23-05 - Version 3.0.17-ga
    - Fixed BUG#7686, Timestamp key column data needed "_binary'" stripped for
      UpdatableResultSet.refreshRow().
    - Fixed BUG#5874, Timestamp/Time conversion goes in the wrong 'direction'
      when useTimeZone='true' and server timezone differs from client timezone.
   - Fixed BUG#7081, DatabaseMetaData.getIndexInfo() ignoring 'unique'
     parameter.
   - Support new protocol type 'MYSQL_TYPE_VARCHAR'.
   - Added 'useOldUTF8Behavoior' configuration property, which causes
     JDBC driver to act like it did with MySQL-4.0.x and earlier when
     the character encoding is 'utf-8' when connected to MySQL-4.1 or
     newer.
   - Fixed BUG#7316 - Statements created from a pooled connection were
     returning physical connection instead of logical connection when
     getConnection() was called.
   - Fixed BUG#7033 - PreparedStatements don't encode Big5 (and other
     multibyte) character sets correctly in static SQL strings.
   - Fixed BUG#6966, connections starting up failed-over (due to down master)
      never retry master.
    - Backported SQLState codes mapping from Connector/J 3.1, enable with
      'useSqlStateCodes=true' as a connection property, it defaults to
      'false' in this release, so that we don't break legacy applications (it
      defaults to 'true' starting with Connector/J 3.1).
    - Fixed BUG#7601, PreparedStatement.fixDecimalExponent() adding extra
      '+', making number unparseable by MySQL server.
    - Escape sequence {fn convert(..., type)} now supports ODBC-style types
      that are prepended by 'SQL_'.
    - Fixed duplicated code in configureClientCharset() that prevented
      useOldUTF8Behavior=true from working properly.
    - Handle streaming result sets with > 2 billion rows properly by fixing
      wraparound of row number counter.
    - Fixed BUG#7607 - MS932, SHIFT_JIS and Windows_31J not recog. as
      aliases for sjis.
    - Fixed BUG#6549 (while fixing #7607), adding 'CP943' to aliases for
      sjis.
    - Fixed BUG#8064, which requires hex escaping of binary data when using
      multibyte charsets with prepared statements.
    - Fixed BUG#8812, NON_UNIQUE column from DBMD.getIndexInfo() returned inverted
      value.
    - Workaround for server BUG#9098 - default values of CURRENT_* for
      DATE/TIME/TIMESTAMP/TIMESTAMP columns can't be distinguished from
      'string' values, so UpdatableResultSet.moveToInsertRow() generates
      bad SQL for inserting default values.
    - Fixed BUG#8629 - 'EUCKR' charset is sent as 'SET NAMES euc_kr' which
      MySQL-4.1 and newer doesn't understand.
    - DatabaseMetaData.supportsSelectForUpdate() returns correct value based
      on server version.
    - Use hex escapes for PreparedStatement.setBytes() for double-byte charsets
      including 'aliases' Windows-31J, CP934, MS932.
    - Enable compression from client -> server if "useCompression=true"
    - Try all addresses for a given hostname, in case someone has IPv6 enabled.
    - Added support for the "EUC_JP_Solaris" character encoding, which maps
      to a MySQL encoding of "eucjpms" (backported from 3.1 branch). This only
      works on servers that support eucjpms, namely 5.0.3 or later.


Thanks in advance.
Back to top
View user's profile Send private message
NightMonkey
Guru
Guru


Joined: 21 Mar 2003
Posts: 356
Location: Philadelphia, PA

PostPosted: Thu Jul 28, 2005 12:18 am    Post subject: Reply with quote

An update:

After removing the mentioned new RDEPENDS, the ebuild compiled fine, and I was able to use it to connect to a remote MySQL DB with OpenOffice 2. So, can we remove those dependencies, please? Or make them into options, via USE flags? Thanks.
Back to top
View user's profile Send private message
matttions
Guru
Guru


Joined: 19 Jul 2004
Posts: 338

PostPosted: Tue Aug 09, 2005 10:43 am    Post subject: Reply with quote

8O

Hi..
I'm tying to do the same ...

just have erased the RDEPEND from the official tree...

have you opened a bug?
_________________
gentoo ... l'unico pinguino da corsa
Back to top
View user's profile Send private message
NightMonkey
Guru
Guru


Joined: 21 Mar 2003
Posts: 356
Location: Philadelphia, PA

PostPosted: Wed Aug 17, 2005 11:07 pm    Post subject: Reply with quote

matttions wrote:
8O

Hi..
I'm tying to do the same ...

just have erased the RDEPEND from the official tree...

have you opened a bug?


Here's the bug: https://bugs.gentoo.org/show_bug.cgi?id=102915
Back to top
View user's profile Send private message
azwr
n00b
n00b


Joined: 06 Aug 2004
Posts: 49

PostPosted: Fri Sep 09, 2005 10:14 pm    Post subject: Reply with quote

i was digging around a bit, and apparently both jta and jdbc2-stdext were provided in the mysql-connector-java .jar file itself, whereas it's now been seperated out as a seperate fetch. however, i notice that netbeans still packages both of these jar files in it's own distfile. so if the point was to provide a method for one download of jta and not replicating it across multiple packages ... it's failed.

additionally, the jar for jta is only like 8kb ... it seems like less of a hassle just to leave it contained in each package that needs it instead of splitting it out. the fetch seems to cause more concern and problems than just letting jta and jdbc2-stdet be replicated on the system. just my 2cents.

~andrew
Back to top
View user's profile Send private message
NightMonkey
Guru
Guru


Joined: 21 Mar 2003
Posts: 356
Location: Philadelphia, PA

PostPosted: Sat Sep 10, 2005 1:44 am    Post subject: Reply with quote

azwr wrote:
i was digging around a bit, and apparently both jta and jdbc2-stdext were provided in the mysql-connector-java .jar file itself, whereas it's now been seperated out as a seperate fetch. however, i notice that netbeans still packages both of these jar files in it's own distfile. so if the point was to provide a method for one download of jta and not replicating it across multiple packages ... it's failed.

additionally, the jar for jta is only like 8kb ... it seems like less of a hassle just to leave it contained in each package that needs it instead of splitting it out. the fetch seems to cause more concern and problems than just letting jta and jdbc2-stdet be replicated on the system. just my 2cents.

~andrew


Hmm... But if fetch is turned on for licensing reasons, then that would seem to imply that just using what is included would mean that whatever the vehicle for getting the source was, it would mean fetch restriction would still be required for the combined source, right?
Back to top
View user's profile Send private message
azwr
n00b
n00b


Joined: 06 Aug 2004
Posts: 49

PostPosted: Sat Sep 10, 2005 4:42 am    Post subject: Reply with quote

I was confused by that too ... but the jta jar and jdbc2-stdext are both definitely in the netbeans package without a fetch restriction. I wonder if there just is an incongruency in the way different maintainers are handling the liscense?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum