IANADE (I am not a Debian expert), but I read the blurb about Debian packaging. I was left with the understanding, as stated, that a /debian directory in our "up stream" SVN is only for "Debian native" packaging, and that is not the norm for most packaging.
I would say that the Hamlib project maintains (should maintain) its code in a distro-neutral form. We would then be regarded as "Debian non-native" -- we intend to get packaged by Fedora, Ubuntu, and whoever will have us. That is how (as I understand it) most all packages are treated. Only those that are only intended to work in a Debian-only environment would be "native".
So, if that's all correct (and IANADE), we should not have a /debian directory any more than we have a /fedora directory, etc. The only reason IMO to keep it is if it would seriously break somebody's build process, and I don't think we've heard about any problems like that (yet).
My 2c worth.
73 Martin AA6E
Okay, I'm swayed by Pat's comments... If the debian/ directory in svn
might be useful to somebody, lets not remove it. Instead, I will sync
it up with the latest from Debian and we can aim to keep it in sync
Pat, to answer your questions:
Its not that the tools don't work -- I think you probably could build a
Patrick Ouellette wrote:
> Has the build process for hamlib changed in 2 years? Do the Debian
> tools (dpkg-buildpkg and others) work properly with the debian/ in svn?
package from the current debian/ in svn. The problem is that the
package you would get would be a confused and somewhat dysfunctional
mess because debian/ is so stale.
You'd end with a Debian package containing the current 1.2.11svn source,
but the package would be called "hamlib_184.108.40.206-3" (from the last time
debian/changelog was synced up).
More importantly, the current svn debian/rules isn't actually valid.
That files doesn't include any handling for the (more recent?) 'rs' or
'spid' libraries at all, and there have been fixes to the install paths.
And there have been some build-depends changes.
And finally, there is a security fix which has been applied to Debian's
package but has not yet been integrated into the hamlib source (the
"embedded libltdl problem" which I will post under separate cover).
73 de KA6MAL
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
Hamlib-developer mailing list