[
https://issues.apache.org/jira/browse/THRIFT-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546437#comment-13546437
]
Marco Matarazzo commented on THRIFT-1825:
-----------------------------------------
Roger,
I didn't use it because I like to have control on the packaging steps, and
creating a symbolic link it's not a big issue. Maybe moving the folder on his
standard, expected position would make it easier to notice it's there (it took
a while for me), but if it's "dirty" to your eyes (it's not something you
actually mantain, in fact) you can just leave it the way it is, IMHO. I believe
someone that is going to build a debian package can ignore how to create a
debian folder from scratch, but for sure he must know how to use it when it's
already there and should be able to hack around a bit and find it.
BTW, I did exactly the same steps the script does, except I'm not deleting
the debian link because I like to have it there, I'm adding -us -uc switches to
dpkg-buildpackage as I can't/won't sign resulting packages, and I'm adding a -d
for 0.8.0 under Ubuntu 12.04 because I know I can ignore the libmono-dev broken
dependency warning as mono is there with just a different package name.
Just my two cents, with a big IMHO disclaimer on top of everything.
> Debian Packaging: cpp libs no longer included since 0.8
> -------------------------------------------------------
>
> Key: THRIFT-1825
> URL: https://issues.apache.org/jira/browse/THRIFT-1825
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.8, 0.9
> Environment: Ubuntu Linux 12.04
> Reporter: Marco Matarazzo
> Attachments: debian_cpp_lib.patch
>
>
> From Thrift 0.8, cpp libs are no longer included in libthrift0 package.
> I'm attaching a very small patch that solves the issue; though I'm not an
> expert of debian packaging and I worked it out through a little hacking, it
> should work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
