Re: [gentoo-dev] New eclass: ros-catkin.eclass, new USE_EXPAND: ROS_MESSAGES, new categories: dev-ros and ros-meta for review.

[Alexis Ballier]

On Thu, 17 Sep 2015 18:36:06 +0200
Alexis Ballier  wrote:

> Hi all,
> 
> As part of an effort of bringing ros (http://www.ros.org/) to Gentoo,
> I've come up with the following design:
> 
> ros-catkin.eclass that is a template, merging all common code for
> catkinized ros packages.
> 
> ROS_MESSAGES will be a new USE_EXPANDed variable: ROS is message
> based, processes write and listen to some topic, and a topic is typed
> with a message. Messages are defined by simple text files but are then
> pre-processed for easy usage in C++, Python & co.
> 
> Several packages are usually bundled in a single repository, with a
> meta-package pulling all the others. Hence, I came with two new
> categories: dev-ros for single packages, ros-meta for those
> meta-packages.
> 
> Some numbers:
>  /bin/ls ros-meta | wc -l
> 52
>  /bin/ls dev-ros | wc -l
> 350
> 
> 
> I think maybe half of them are in a state that they can be added to
> gentoo-x86.
> 
> 
> ebuild example:
> 
> $ cat roslib-1.12.2.ebuild 
> # Copyright 1999-2014 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> # $Header: $
> 
> EAPI=5
> 
> ROS_REPO_URI="https://github.com/ros/ros";
> KEYWORDS="~amd64 ~arm"
> PYTHON_COMPAT=( python{2_7,3_3,3_4} )
> ROS_SUBDIR=core/${PN}
> 
> inherit ros-catkin
> 
> DESCRIPTION="Base dependencies and support libraries for ROS"
> LICENSE="BSD"
> SLOT="0"
> IUSE=""
> 
> RDEPEND="
> dev-python/rospkg[${PYTHON_USEDEP}]
> dev-libs/boost:=[threads]
> dev-ros/rospack
> "
> DEPEND="${RDEPEND}
> test? ( dev-ros/rosmake ros-meta/ros )"
> 
> 
> 
> 
> 
> Eclass inlined at the end.
> 
> Best regards,
> 
> Alexis.


Since there hasn't been comments in a few days, I'm proceeding with the
above plan. (with hasufel's eclass review taken into account of course)

Alexis.

[gentoo-dev] Team leader(s) election meeting

[Alexander Berntsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Friends,

please set your availability[0] for our next meeting, where we will
elect team leader(s). We should probably also clear up the memberships
as most of the members haven't been active in months (some have
actually never been active at all).

On a related note this would be a good time for anyone interested in
contributing to Portage to show up. If you have any questions on how
to get into Portage hacking, the current team leaders will be there to
answer your questions to the best of our abilities.

Please feel free to distribute this email to non-devs that are
interested in contributing to Gentoo or Portage. There are several
other distros using Portage, but we rarely hear anything from any of
them except for the Google guys every now and again. Then there's the
matter of our users themselves. Surely it is in everyone's interest
that this project doesn't stagnate.

Thanks.

[0]  
- -- 
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWASmgAAoJENQqWdRUGk8ByVIP/RZq9+SDmlrmBi4Cawz/jhps
Rz0DiYnlHYU3T9EEHnjAFGgkAoIo04arAzP1CC8j1bPoQe6bHMSn29RbLZ/Yu05h
sdiPVmBN9v+/5X6XIcnXk/66Bi05msTse/BOjGOtqafUrpgvundn4BkU/eSuAH00
OHSNB53HvAQCb9ap7PvuL2ZVoIF//BjdpzVO8wDm+U3rJ6hUv5em+F54iXHU8X5h
HYg7YRnn0BLJEUg+F3S/x3sreT/N9aWqRIXmcNm1X6k7ov+tHPfCOOzjTfxpnDJ1
Aio97DmapbATwKsLv51cp3Kth9eOgxZHQ2cNWerING/UoNl8d3M0WdXqdKuELPLC
b9sBQmVXQDlIm+4ZbynNb2byPVQY1NJVvenD83H5pPJgOfdA+Dr7RI35MLFgur+F
IY1S4p7lrHtxm/89aAfF69he3lJHWPd97mnw3I4X7odkTxsURgpn7XhihLyTW2pw
UJejQgujeAhkr4ydfDPJyboMntXtbXwzDk4UYrMNeOykjuTB4J51jaGJpJT1KL4C
WR7fVk8+c1aaWzjwhSq92CKuZmRxywdTu58LACE9o0CkT76TCkJKmHUzUBIYDQmY
VRGNHDMRF6PcKXFDBlE4SCkb9LOMQyUgJu7OVM9IiTFCE9teG0QU2NjsGWMZE7JJ
8Vr3ZBV4mjaNtez/MbkD
=JSPa
-END PGP SIGNATURE-

Re: [gentoo-dev] Team leader(s) election meeting

[Ian Stakenvicius]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 22/09/15 06:12 AM, Alexander Berntsen wrote:
> Friends,
> 
> please set your availability[0] for our next meeting, where we
> will elect team leader(s). We should probably also clear up the
> memberships as most of the members haven't been active in months
> (some have actually never been active at all).
> 
> On a related note this would be a good time for anyone interested
> in contributing to Portage to show up. If you have any questions
> on how to get into Portage hacking, the current team leaders will
> be there to answer your questions to the best of our abilities.
> 
> Please feel free to distribute this email to non-devs that are 
> interested in contributing to Gentoo or Portage. There are
> several other distros using Portage, but we rarely hear anything
> from any of them except for the Google guys every now and again.
> Then there's the matter of our users themselves. Surely it is in
> everyone's interest that this project doesn't stagnate.
> 
> Thanks.
> 
> [0]  
> 

This is the Portage team i assume?  It seems implied but i see
nothing explicit so i just wanted to confirm.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREIAAYFAlYBXfIACgkQAJxUfCtlWe1AuwEAgHetp6IZEF7Gcq1DF/Q4EbcJ
Qoj1VnZSC6z7b2t9JzMBAIQX2zgFTwHVk4P46ADByJk8RHAK+Dgi5Ro3gUqlmMqB
=yvyE
-END PGP SIGNATURE-

Re: [gentoo-dev] Team leader(s) election meeting

[Alexander Berntsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 22/09/15 15:56, Ian Stakenvicius wrote:
> This is the Portage team i assume?  It seems implied but i see 
> nothing explicit so i just wanted to confirm.
Yes. I merely CC-ed dev FYI.

- -- 
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWAV4iAAoJENQqWdRUGk8BSyMP/ArgZgHv+6Z3B+bfJ348/K9W
QJdTP3G31bwcJn8rH0C4uMmtMN/A7EFrG32w8skk05Eikup/oGIC992PvKpJZmBW
DHGbIWCP8CP4LUCs8/l3d06SPd5kolx0LVD49FnDwF1M5Jsw9cf1iAkusKrdrvNC
DIC/JbG9zCSH52kjG2FKwDl/ZPthCBmlNfbWM7ZRSd3MIapKGwws8CFwZT0a8SfJ
2qbQA4YvpbDfkB88BJxq1XLAEdYO0nb7b/xHmDCaHwRDT368iXT55VGU2a2TDsij
VJRNmCl8T+3k3o7u5uRF/oYKPGbLMLF4x5HGDkGn4LM269NhnycBlL9abpnIWfrH
IxjsKFWlDy2DoSgThjsnf+DIcTciZ5KMo3t+JHzB+Nquh5Vujy1Q/EE4XIPAZjLm
0a1DCo1wUfnAk3DEEhHyAGcvVK5kJnBbTB4BPrAl0ne7yQPcr1OUEKPvqtSXRZ3r
i6PAOTTq8A3C4ikFCuwg59bjLNIQFCNR14/8QH2TmobT4fN880CIA5K9+8VJxHhe
ddPihre1+VyF0gDQNM3DAe+mq+dDZjqS+d3MFiRwMhX7lNJJxlVb5ugsYuq04Eko
oqEFS4Ls6eQNUEPspCf0tK1W1bp6O/2iryWTTDWOs3FprbR4oAS7JCJRviLt0sH/
nP30LeuELsFLZ/MFCiPH
=oKZl
-END PGP SIGNATURE-

Re: [gentoo-dev] New eclass: ros-catkin.eclass, new USE_EXPAND: ROS_MESSAGES, new categories: dev-ros and ros-meta for review.

[wireless]

On 09/22/2015 03:26 AM, Alexis Ballier wrote:

On Thu, 17 Sep 2015 18:36:06 +0200
Alexis Ballier  wrote:


Hi all,

As part of an effort of bringing ros (http://www.ros.org/) to Gentoo,
I've come up with the following design:

ros-catkin.eclass that is a template, merging all common code for
catkinized ros packages.

ROS_MESSAGES will be a new USE_EXPANDed variable: ROS is message
based, processes write and listen to some topic, and a topic is typed
with a message. Messages are defined by simple text files but are then
pre-processed for easy usage in C++, Python & co.

Several packages are usually bundled in a single repository, with a
meta-package pulling all the others. Hence, I came with two new
categories: dev-ros for single packages, ros-meta for those
meta-packages.

Some numbers:
  /bin/ls ros-meta | wc -l
52
  /bin/ls dev-ros | wc -l
350


I think maybe half of them are in a state that they can be added to
gentoo-x86.


ebuild example:

$ cat roslib-1.12.2.ebuild
# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

EAPI=5

ROS_REPO_URI="https://github.com/ros/ros";
KEYWORDS="~amd64 ~arm"
PYTHON_COMPAT=( python{2_7,3_3,3_4} )
ROS_SUBDIR=core/${PN}

inherit ros-catkin

DESCRIPTION="Base dependencies and support libraries for ROS"
LICENSE="BSD"
SLOT="0"
IUSE=""

RDEPEND="
 dev-python/rospkg[${PYTHON_USEDEP}]
 dev-libs/boost:=[threads]
 dev-ros/rospack
"
DEPEND="${RDEPEND}
 test? ( dev-ros/rosmake ros-meta/ros )"





Eclass inlined at the end.

Best regards,

Alexis.



Since there hasn't been comments in a few days, I'm proceeding with the
above plan. (with hasufel's eclass review taken into account of course)

Alexis.


Hi Alexis.

As  a gentoo user, an ebuild hacker and engineer, I'd suggest you 
include a wiki page for gentoo users, to document the gentoo specific 
issues. I'm a big fan of the new gentoo wiki. Access to either a 
'virtual robot', or where to purchase devices that use ROS, would at 
least greatly facilitate folks  to participate with ROS  robotics codes. 
 Include links to  the main  ROS repos, and relevant other urls.

For example; one of the common things missing in such projects is
an example linux kernel, stripped to optimize only the size and 
performance of the ROS devices and software. Showing this kernel .config

would be keen. At list discussion why some of the key kernel configs
are select is sorely missing in the world of robotic and UAVs, imho.

 You may also what to include 'hooks' to relevant and commonly used 
embedded boards with ROS hardware. I am working on clustering for gentoo 
using mesos + zookeeper + apache-spark (we have 2/3 in overlays now). 
Lots of robotic work now attempts to use the power of the cluster over 
an Rf link and/or use many robots computational resources, as a mere 
node in a cluster.



I for one have been looking for such a project, if It combines
robotics issues with (UAV) issues. After all, all UAVs are robots, with 
additional constraints.



hth,
James

Re: [gentoo-dev] New eclass: ros-catkin.eclass, new USE_EXPAND: ROS_MESSAGES, new categories: dev-ros and ros-meta for review.

[Alexis Ballier]

Hi,
 
> Hi Alexis.
> 
> As  a gentoo user, an ebuild hacker and engineer, I'd suggest you 
> include a wiki page for gentoo users, to document the gentoo specific 
> issues.

Yes, this is planned. That part would be short though. The real work is
done in upstream wiki :)


> I'm a big fan of the new gentoo wiki. Access to either a 
> 'virtual robot', or where to purchase devices that use ROS, would at 
> least greatly facilitate folks  to participate with ROS  robotics
> codes. Include links to  the main  ROS repos, and relevant other urls.
> For example; one of the common things missing in such projects is
> an example linux kernel, stripped to optimize only the size and 
> performance of the ROS devices and software. Showing this
> kernel .config would be keen. At list discussion why some of the key
> kernel configs are select is sorely missing in the world of robotic
> and UAVs, imho.

For the kernel part, I don't think this would happen: It *really*
depends on your needs. For the record, I've been running this on desktop
computers and several arm boards (rpi, odroid, udoo for instance). For
the arm part, if you can live with mainline kernel (kernel.org) lacking
some drivers (or even doing the mainlining yourself), then good,
otherwise you'll be stuck with the bugs of old vendor kernels...

In the end, you can see this as an add-on to anything that you can run
gentoo on :)

For the links to tutorials, ROS wiki is very good, and this is what
happens to be in the HOMEPAGE field of the ebuilds. (use eix)


Finally, for UAVs, I've seen some projects using linux, but usually
a more dedicated realtime OS running on a microcontroller is used (some
are arduino based) and then controlled via serial port from ROS that
will handle the computing intensive part (SLAM, localization, sensor
fusing, etc.).

Alexis.

[...]

Re: [gentoo-dev] Updating all Manifest to contain SHA256 SHA512 WHIRLPOOL

[Justin Lecher (jlec)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi there,

I did a first fix run.

https://github.com/jlec/gentoo/commit/0df86dcca0aa981fa7bdba633653697e2b
40781c

Although my script checks whether the size and SHA256 changed, but
better you could also take a look.

Thanks,
Justin
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0

iQJ8BAEBCgBmBQJWAaq2XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF
OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiu4oQALR2JdGsAYF9UoTefwH6pic6
LZQWlkiMrvAY8SvsE6g9gW9IDzSzuZtbi4EgN0nkvYWskN9KlyUyMOQH/snbpAsd
eiijG98pFNqEa4nBJBDuBUjPPjZ8M30i6/dsHMEW3HCgi73Va1Rr/6U5l+eO111b
W578EhpAqcIhRenr9ssbUEA0EdTKsZYdbtpZDGrrXy9+Zw0ZOwAXqQyeylML1kJN
usr08KHyqi9VMom19G1EeENO9XTKU9hHoCkHjSnfsl/Zi3KJT7VQXhBLIEcxuX8m
WeGQ+tGA0Ih1G1zNfepUle3eCV1gaXu6h+m+wUDk2enMCJPIFtDUbI/gDOvf3Gny
uZhl9MHFUcYuGiroAXHiZUEGvvhjDMXwciUavvsR/813L+uqt+rgiDA7YMNmVjeV
dACcaxH76zHweHQh5IKm4V63a2cuwLvpq6WVviiwUPNrI32B4C8WAM79SfbQDILL
Il4QJvTYJKLfgcz2RCsnfBIT5jdvrmJLD6yozGpHP8/EaBtiAhvtAkT5H7JTv8yv
/9QR5rMoEQczeJGJVV+nPvSePZs1WxMAP5RraElL/Jdu7nnZf++WD/H9YmnvXZfi
TJqOyETEJ+tisyx5z/EXaBAS0hZVl7Hswu1gItZoiDEF0FdOgvJU0tJA/rOSftmB
Nv4KyknRPPm8pwcAn4z8
=WapW
-END PGP SIGNATURE-

Re: [gentoo-dev] Updating all Manifest to contain SHA256 SHA512 WHIRLPOOL

[Tim Harder]

On 2015-09-22 15:23, Justin Lecher (jlec) wrote:
> https://github.com/jlec/gentoo/commit/0df86dcca0aa981fa7bdba633653697e2b
> 40781c

> Although my script checks whether the size and SHA256 changed, but
> better you could also take a look.

You could open a pullreq against the gentoo github repo and I think
pkgcheck will be automatically run against it. Then look if there are
any remaining MissingChksum reports in the output.

Tim


signature.asc
Description: PGP signature