[ 
https://issues.apache.org/jira/browse/THRIFT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912282#action_12912282
 ] 

Roger Meier commented on THRIFT-71:
-----------------------------------

please commit this!

I would like to merge Eric Evans patches from 
http://git.debian.org/?p=collab-maint/thrift.git with latest patch 
[^thrift-71_v7.patch] hopefully before 0.5 release, but we need a starting 
point within repo.

The important thing is, that we can at least *deploy Thrift compiler as Debian 
package* with each release, just as we do with win32 Thrift Compiler or Maven.

On Question for me is:
how do we get the VERSION define from config.h to relevant files for each 
release?
e.g. lib/csharp/ThriftMSBuildTask/Properties/AssemblyInfo.cs

debian/changelog has to be edited manually for each release, but the rest 
should be fully automated.
        



> Debian packaging for thrift
> ---------------------------
>
>                 Key: THRIFT-71
>                 URL: https://issues.apache.org/jira/browse/THRIFT-71
>             Project: Thrift
>          Issue Type: Improvement
>         Environment: debian stable (etch); probably will work on lenny, but 
> untested
>            Reporter: Eric Anderson
>            Priority: Minor
>         Attachments: debian-packaging.patch, thrift-71.patch, 
> thrift-71_v2.patch, thrift-71_v3.patch, thrift-71_v4.patch, 
> thrift-71_v5.patch, thrift-71_v6.patch, thrift-71_v7.patch
>
>
> We're using thrift on Debian, so I wanted to have a package for easier
> installation by other users.
> Attached is a patch to add packaging for debian to the
> thrift-20080411p1 release.  It includes two bug fixes to make the
> tests work reliably: 1) adding /usr/share/java/commons-lang.jar to the
> search path for the java tests, and 2) sleeping 1 second after
> starting the server for the python tests.  If the patch is accepted,
> the maintainer should probably be set to the thrift mailing list,
> rather than the example mailing list address I used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to