Re: Package Guidelines: Should config files follow upstream or Fedora defaults?

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

 



Hi,
one more question about the subpackage approach

On 10/8/18 12:39 AM, Dominik 'Rathann' Mierzejewski wrote:
>> 2) ship example config file as real config file, with upstream's example
>>    config activated
> 
> Ship this configuration in a subpackage (sshguard-iptables).  Use rich
> dependencies to have it auto-installed if iptables-services is installed.
> 
>> 3) ship custom config file preconfigured for Fedora defaults
> 
> Ship this configuration in a subpackage (sshguard-firewalld). Use rich
> dependencies to have it auto-installed if firewalld is installed.

This implies that the spec contains multiple /etc/sshguard.conf files. I
can ship them as %doc sshguard.conf.<backend>, and then cp them to
sshguard.conf during %post <subpackage>, but then no package would own
that file, right?

I can of course create separate packages with separate spec files for
the config, but can this also be made to work with subpackages?

Best,
Christopher
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx




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

  Powered by Linux