On Mon, Nov 28, 2011 at 5:42 PM, Bryan Duxbury <br...@rapleaf.com> wrote: > Is there some way that we can combine our efforts? I'd love it if the work > Eric does can become part of the stuff Thrift uses to publish releases. Is > this feasible?
On my end, I would need the build to create distinct artifacts for each of the components (compiler and each lib). This also implies that there would need to be packaging source (think debian/) for each, instead of just the one top-level. The reason for this is that the whole thing covers too many disciplines to have a single person (at least this person) maintaining it all throughout a Debian release life-cycle. I would still need to maintain a fork because the packaging and upstream source are not expected to move in lock-step (i.e. there can be many package releases for each upstream version), but they could be kept closely synced. > On Mon, Nov 28, 2011 at 4:19 PM, Eric Evans <eev...@apache.org> wrote: >> >> On Mon, Nov 28, 2011 at 4:52 PM, Jake Farrell <jfarr...@apache.org> wrote: >> > I have been looking into trying to get the thrift compiler and libs into >> > debian/ubuntu packages to help make it easier for people to install and >> > start using thrift. Eric Evans, a Cassandra committer, has all ready >> > started >> > this as a sub project contained within github. He syncs with our code base >> > and then runs scripts against it to create separate packages for the >> > compiler, python and java to package. I've asked Eric to not submit his >> > intent to package to debian so that we can come up with one unified way to >> > handle all the packaging and add this into our release process moving >> > forward. >> >> The ITPs are already submitted: >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648451 >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648452 >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648453 >> >> If there is consensus within the Thrift project that I not move >> forward, I will honor that and not upload to Debian (but that's me, I >> can't promise the next person won't come along and upload what they >> want). >> >> If there is a credible plan for taking over these ITPs in order to do >> it according to your own preferences, then I will step aside and >> assign these ITPs to you. >> >> Otherwise I plan to move forward. >> >> > We will also need to find a debian mentor or sponsor until we can >> > publish these artifacts on our own. >> >> -- >> Eric Evans >> eev...@apache.org > > -- Eric Evans Acunu | http://www.acunu.com | @acunu
