[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ubuntu-motu
Subject:    RFC: lucene/solr projects merged upstream
From:       mat () wibbly ! org ! uk (Mat Scales)
Date:       2011-07-29 13:33:09
Message-ID: CACv6RzubVdqkvuToady=zVH1=Ta63kAvpexrEHDXAYTbt3JjYQ () mail ! gmail ! com
[Download RAW message or body]

Hello,

I am intending to package the latest versions of apache-solr and lucene.
However, upstream the Solr and Lucene projects have been merged so they
share a source package.

I am requesting comments on how best to deal with the situation.

Currently, the source package lucene2 provides liblucene2-java and
liblucene2-java-doc. The solr source package provides solr-common,
solr-tomcat and solr-jetty.

How I would imagine the resolution is:

* Merge the lucene2 source tree with the solr one
* Merge the latest upstream
* Make the solr source package now provide solr-common, solr-tomcat,
solr-jetty, liblucene-java and liblucene-java-doc
* Update the Depends: of packages that depend on lucene to the new binary
package names
* Remove the lucene2 source package and its binary products from Ubuntu

Outstanding questions:
* Since the latest version of Lucene is 3.4.0, liblucene2-java no longer
makes sense as a name. Should it be liblucene-java or liblucene3-java now?
* Should the debian/changelogs of the two packages be merged into one?
* Would the new lucene packages need to have Provides, Conflicts or Breaks
sections in debian/control to deal with the transition?

Thank you for your time

Mat Scales
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20110729/ee4b6d37/attachment.html>

[prev in list] [next in list] [prev in thread] [next in thread]