Hi, I'm trying to package ntp-refclock [1], which is a wrapper for reference clock drivers from ntpd to make them usable with other NTP implementations. The package builds code from two projects and I'm not sure what should be the version and release. The guidelines for versioning don't seem to cover this odd case. ntp-refclock-0.1 is combined with ntp-4.2.8p10. The majority of the code compiled for the package comes from ntp (the drivers and some code that the drivers need), so I think the version or release needs to include the ntp version.

On Mon, Jan 22, 2018 at 10:30:43AM -0500, Jarod Wilson wrote: > On 2018-01-22 5:07 AM, Miroslav Lichvar wrote: > > ntp-refclock-0.1 is combined with ntp-4.2.8p10. The majority of the > > code compiled for the package comes from ntp (the drivers and some > > code that the drivers need), so I think the version or release needs > > to include the ntp version. > > Are they split into separate sub-packages, or is it just one big package > built from the two sources? In the former case, I've seen packages just > independently version sub-packages. There is just one package. It contains only one executable which includes all drivers (that were enabled in ntp configuration) with the wrapper that allows the drivers to run.

On Tue, Jan 23, 2018 at 11:57:44AM +0100, Dominik 'Rathann' Mierzejewski wrote: > On Monday, 22 January 2018 at 16:45, Miroslav Lichvar wrote: > > There is just one package. It contains only one executable which > > includes all drivers (that were enabled in ntp configuration) with the > > wrapper that allows the drivers to run. > > In that case, I'd add > # includes ntp drivers and some code > Provides: bundled(ntp) = 4.2.8p10 Ok, that looks good. Thanks. I assume with the provides there is no need to put the ntp version in the release string as an "extraver" per the guidelines.