Is category NI at ros-pkg the bug tracker to use?

For the .pc files, lsb_release gives results for archlinux that the
original Makefile writer did not anticipate. Easy fix if ROS isn't
trying to parse that __VERSION__ field.


-traveler
On 6/04/2012 7:45 p.m., Jochen Sprickerhof wrote:
> Hi Traveler,
>
> * Traveler <traveler.hauptman@iit.it> [2012-04-06 19:26]:
>> ROS's openni-drivers bundle Makefile needs work to make in useable
>> with the archlinux packager (mainly assuming the install root is '/'
>> needs to be generalized to $DESTDIR). I'm not too swift with hg. Can
>> I just post a patch file? To where?
> You could put them into the bug tracker ;).
>
>> Also, from a packaging perspective, it's nice to be able to use the
>> original sources. I already have archlinux packages for openni, etc,
>> but there is some magic happening with pkgconfig.pc files... any
>> chance those could be pushed upstream?
> Apart from the .pc changes (which are rather minor afair), we have quite
> some patches in there and are working on getting them in better shape.
> I have a change the variants in PCL already to be closer to upstream
> (maybe that would be an example for arch as well) and the stuff in the
> hg will hopefully get better soon.
>
>> Also, in those .pc files, is ROS using the info injected into __VERSION__?
> Afaik not, why do you ask?
>
>> -traveler
> Cheers,
>
> Jochen
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users