Re: best way to package debug/diagnostic build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 14 Aug 2017 12:26:49 -0400
John Dennis <jdennis@xxxxxxxxxx> wrote:

> Scenario: A previously shipping RPM has the capability to be built
> with diagnostic and other debugging features. This has always been
> turned off and should be turned off for any production deployment.
> However the ability to install a version of the package with these
> features enabled would be immensely useful.
> 
> Here is how I thought I would do this: add a "diagnostic" subpackage 
> that includes only the binary with the diagnostic build. There will
> be a file conflict only on the binary and users will have to look for
> the diagnostic subpackage to ascertain which build is executing.
> 
> What is the best way to add alternate builds in an RPM? Do we have 
> existing precedent? I didn't find any guidance in the packaging 
> guidelines, the closest I could find was the "Conflicts" doc 
> (https://fedoraproject.org/wiki/Packaging:Conflicts) which didn't
> really address the issue.

Take a look at the curl package and how it produces curl-minimal.

Paul.
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux