Re: virtual packages, libraries, and dpkg-shlibdeps

j...@acorntoolworks.com (J.T. Conklin) writes: > I've tried adading a debian/shlibs file to map the library name to the > virtual package name. I may be just getting the syntax wrong, or perhaps > I'm barking up the wrong tree. It turns out I had a problem in the *.shlibs files whe

Re: Preference for build or debhelper installing systemd unit files?

Andreas Henriksson <andr...@fatal.se> writes: > Hello J.T. Conklin, > > On Wed, Jan 11, 2017 at 09:49:43AM -0800, J.T. Conklin wrote: >> This question is related to components Dell EMC (my current employer) >> are contributing to the Linux Foundation's openswitch pro

virtual packages, libraries, and dpkg-shlibdeps

This question is related to components Dell EMC (my current employer) are contributing to the Linux Foundation's openswitch project. Our architecture is made up of platform independent components/packages, which are adapted to specific hardware platforms (ie. switches) by with platform specific

Re: Debian packaging for packages that provide the same files

Niels Thykier writes: >> A complication is that each platform config package installs the same >> set of files, so the normal package build technique of having all files >> being installed to a common staging directory and each package's files >> being selected by the

Re: Preference for build or debhelper installing systemd unit files?

Niels Thykier writes: >> My question, in the case where the same organization/people are >> responsible for both the software and the debian packaging, is whether >> there is a preference of which method is used. > If you are (working on/with) upstream and doing the

Preference for build or debhelper installing systemd unit files?

This question is related to components Dell EMC (my current employer) are contributing to the Linux Foundation's openswitch project. With debhelper, systemd unit files can be installed by a package's build (ie. the Makefile installs them in $DESTDIR/lib/systemd/system/...) or they can be put in

Debian packaging for packages that provide the same files

This question is related to components Dell EMC (my current employer) are contributing to the Linux Foundation's openswitch project. Dell is contributing platform independent packages that depend on a platform specific package that provides configuration files. For our own internal use, we've

Re: Seeking recommendations wrt. target-specific packages

Thanks Paul for your thoughtful response. You gave me a lot of useful options to investigate. Paul Wise writes: >> We produce network equipment devices, and the project to be released is >> a framework to configure and manage the data plane. > > FYI that sounds a bit related

Re: Seeking recommendations wrt. target-specific packages

On Wed, Jun 8, 2016 at 10:32 AM, Paul Wise Wrote: > On Wed, Jun 8, 2016 at 3:58 AM, J.T. Conklin wrote: > > Before I go ahead with this, I'd appreciate some feedback on this > > approach. Should we plan to use "distribution" or "component" for > > target

Seeking recommendations wrt. target-specific packages

I tried asking this on the deity list and didn't get any bites, I'm hoping I'll have better luck with mentors. At my workplace, our product is built from several dozen target- independent packages, with a small number of target-specific packages. I use the word "target" instead of platform as our