Calling clang packagers: Do you install libclang & the python bindings?

If you are the maintainer of the clang package for one of the major
OSs/distros:

1. Does your clang package install libclang and the python bindings†?

2. If not, is it because of anything that needs to be changed/added in
  clang's Makefiles/CMakeLists.txt?

The reason I ask: Tools like clang_complete‡ require libclang & the
python bindings. clang_complete solves this problem by shipping its own
copy of the libclang python bindings. I think this is less than ideal.
How do you guarantee that the bindings match the system's libclang, for
one.

I have only checked on a handful of systems, but none of them have the
python bindings:
* Fedora 17's clang package installs /usr/lib/llvm/libclang.so but no
  python bindings.
* On OS X, macport's clang-3.1 package installs
  /opt/local/libexec/llvm-3.1/lib/libclang.dylib and some scan-view
  python files but not the libclang python bindings.
* On my (ancient) Debian 4.0 system, the clang (2.7) package doesn't
  include libclang at all.
* The corresponding clang-devel packages also don't install the python
  bindings.

† bindings/python/clang in the clang source tree
https://github.com/Rip-Rip/clang_complete

If you are the maintainer of the clang package for one of the major
OSs/distros:

1. Does your clang package install libclang and the python bindings??

On FreeBSD we do install libclang but do not install the python
bindings.

2. If not, is it because of anything that needs to be changed/added in
  clang's Makefiles/CMakeLists.txt?

It's just been lack of a request. I'd be happy to add a package if
someone wanted to add a package that needed them. I'd probably add
py-clang and py-clang-devel packages to avoid a python dependency in the
main port.

-- Brooks

I am doing exactly the same for Debian and Ubuntu.

Sylvestre

If you are the maintainer of the clang package for one of the major
OSs/distros:

1. Does your clang package install libclang and the python bindings??

On FreeBSD we do install libclang but do not install the python
bindings.

2. If not, is it because of anything that needs to be changed/added in
clang's Makefiles/CMakeLists.txt?

It's just been lack of a request. I'd be happy to add a package if
someone wanted to add a package that needed them. I'd probably add
py-clang and py-clang-devel packages to avoid a python dependency in the
main port.

I am doing exactly the same for Debian and Ubuntu.

Brooks, Sylvestre, thank you for your replies!

My motivation is that I've written clang-ctags† and I would like to tell
people to just apt-get or port install py-clang, and then they can
git-clone clang-ctags and run it directly, without having to build clang
themselves. But I don't know that anyone actually *uses* clang-ctags
yet, so I don't know if it merits its own package.

Would you consider adding a py-clang package without any package that
directly uses it? What are the "notability" requirements for accepting a
new package such as clang-ctags?

I'd probably add
py-clang and py-clang-devel packages to avoid a python dependency in the
main port.

What's the need for py-clang-devel -- wouldn't py-clang already contain
all the required python files?

Thanks,
Dave.

https://github.com/drothlis/clang-ctags

> Le 26/08/2012 18:53, Brooks Davis a ?crit :
>>> If you are the maintainer of the clang package for one of the major
>>> OSs/distros:
>>>
>>> 1. Does your clang package install libclang and the python bindings??
>> On FreeBSD we do install libclang but do not install the python
>> bindings.
>>
>>> 2. If not, is it because of anything that needs to be changed/added in
>>> clang's Makefiles/CMakeLists.txt?
>> It's just been lack of a request. I'd be happy to add a package if
>> someone wanted to add a package that needed them. I'd probably add
>> py-clang and py-clang-devel packages to avoid a python dependency in the
>> main port.
>>
> I am doing exactly the same for Debian and Ubuntu.

Brooks, Sylvestre, thank you for your replies!

My motivation is that I've written clang-ctags? and I would like to tell
people to just apt-get or port install py-clang, and then they can
git-clone clang-ctags and run it directly, without having to build clang
themselves. But I don't know that anyone actually *uses* clang-ctags
yet, so I don't know if it merits its own package.

Would you consider adding a py-clang package without any package that
directly uses it? What are the "notability" requirements for accepting a
new package such as clang-ctags?

In principle yes since this looks trivial. Ports are typically added
because someone wants them without any formal notability requirement.
So long as clang-ctags uses interfaces that are stable enough to keep
ugprades from being blocked by it, adding a port would have little cost.

>> I'd probably add
>> py-clang and py-clang-devel packages to avoid a python dependency in the
>> main port.

What's the need for py-clang-devel -- wouldn't py-clang already contain
all the required python files?

In FreeBSD land -devel means "non-release snapshot". In this case
arbitrary SVN snapshots to allow feature testing between releases.

-- Brooks

Wearing my SUSE/openSUSE hat on;

If you are the maintainer of the clang package for one of the major
OSs/distros:

  1. Does your clang package install libclang and the python bindings†?

Only libclang.

  1. If not, is it because of anything that needs to be changed/added in
    clang’s Makefiles/CMakeLists.txt?

We use autoconf and it doesn’t seem to install python bindings.

Regards,
ismail