Release as debian package

[Timple]

Thanks for implementing the namechange in #15

Would you be interested in releasing this package so people can apt install ros-melodic-can-dbc-parser?

It's not hard but will take you two hours or so. If you like I can assist with that (I do the same for ublox_gps.

(But please merge #21 first because the install directories are off)

[NewEagleRaptor]

Hi. We plan on doing this but finding the time to do so has been difficult--as you can tell... (our responses to these threads make this apparent--but we're trying to be a bit more diligent!)

Ideally, we'd like to implement a more robust test framework before an official release

[Timple]

Haha, time is an issue everywhere I guess. The backlog is longer than the time available... The first release is some work, any releases after that is 5 minutes of work. So be careful not to aim for perfection before release, you can also add a test framework later.

The buildfarm is another way of making your package available, it's not a certification of any sort :bowtie:

edit: implementation detail: the buildfarm requires all packages in a repo to have the same version number. If you expect a lot of iterations on the raptor_* packages this will also bump the independend can_dbc_parser package. To prevent this you can host the can_dbc_parser in a seperate repo. This will be more initial work though. (This is a considersion, not a suggestion :relaxed:)

[Timple]

Is there any update on the above?

One can also only release a single package from a repo if desired. So only can_dbc_parser. This way there is no need to wait for perfection on the other packages :slightly_smiling_face:

[Timple]

Would you mind if I fork only the can_dbc_parser and release it to the ROS buildfarm? This way you don't have to make the time available.

Qui tacet consentire videtur, ubi loqui debuit ac potuit