Package Details: python2-catkin_pkg 0.4.12-1

Git Clone URL: https://aur.archlinux.org/python2-catkin_pkg.git (read-only)
Package Base: python2-catkin_pkg
Description: catkin package library
Upstream URL: http://wiki.ros.org/catkin_pkg
Licenses: BSD
Conflicts: python-catkin_pkg, python2-catkin-pkg
Provides: python2-catkin-pkg
Submitter: kartikmohta
Maintainer: kartikmohta
Last Packager: kartikmohta
Votes: 7
Popularity: 0.000752
First Submitted: 2017-06-27 21:14
Last Updated: 2019-05-06 18:10

Required by (45)

Sources (1)

Latest Comments

1 2 Next › Last »

lesto commented on 2019-06-20 22:14

this packet itself would not make sense to have since cannot be installed, and that would also break anything depending on this.

Would publish a aur package called python2-argparse that install it by pip (afaik is still present in pip) fix all without requiring any modification to this package?

joaocandre commented on 2019-06-20 21:57

@kartikmohta I am aware of that, but isn't the point of AUR to facilitate that process? As it stands, it is not possible to compile older ROS packages with this package.

kartikmohta commented on 2019-06-15 19:27

@joaocandre If you compile ROS from source yourself, you can use whichever version of Python you prefer. The ROS melodic packages from AUR use Python3 since Python2 would reach EOL soon.

joaocandre commented on 2019-06-15 14:56

catkin_make complains about missing catkin_pkg unless I specifically define the python version to be used as python3.

EDIT: which for me personally is not an issue atm, but implies ROS melodic can't be used on Arch with python2

kartikmohta commented on 2019-06-15 06:13

@joaocandre Why do you need to install python2-catkin_pkg if you already have python-catkin_pkg?

joaocandre commented on 2019-06-14 23:33

The problem, though, is that even if one compiles the argparse manually, it conflicts with python-catkin_pkg, and thus an attempting to install this package will prompt me to either uninstall several core ros packages or break dependencies.

kartikmohta commented on 2019-06-11 21:44

My personal opinion, but I find it odd that people are using Arch and still remain on ROS kinetic when the next ROS LTS (melodic) has been out for more than a year.

BTW, you can use ROS kinetic with Python3 as well, the maintainer of the ros-kinetic-* packages just needs to update the dependencies and set some env variables when compiling.

lesto commented on 2019-06-11 21:31

yes it make sense, since this is a dependency from ROS kinetic that is going to be relevant until 2021, and that is relevant for a lot of people (even if most are going to just use ubuntu xenial)

kartikmohta commented on 2019-06-11 21:07

Given that Python 2 is EOL in about 6 months, does it even make sense to keep maintaining the python2 package? I would strongly recommend people to move to the python3 version.

lesto commented on 2019-06-11 20:34

can we fix it adding to AUR the following PKGBUILD? https://github.com/axilleas/okeanos-archlinux/blob/master/python2-argparse/PKGBUILD