[SSSD] [PATCHES] Make sssd.spec.in work without libini_config >= 1.1.0

Nikolai Kondrashov Nikolai.Kondrashov at redhat.com
Tue Aug 5 15:44:23 UTC 2014


On 08/05/2014 05:59 PM, Nikolai Kondrashov wrote:
> On 08/05/2014 04:31 PM, Lukas Slebodnik wrote:
>> The main purpose of CI should be to test new features, primary on fedora and
>> rhel/centos. In last version of SSSD, we enhanced integration with AD and this
>> last patch will disable this provider on el6 and el7. It is step back.
>>
>> I test sssd from master branch with modified version of epel-6-x86_64.cfg and
>> epel-7-x86_64.cfg. They contain extra repositories with ding-libs-0.4.
>
> This patch was the result of an IRC discussion I had with Jakub, where we
> basically concluded that maintaining packages for *all* the dependencies
> currently and potentially necessary to enable all the (newest) features on at
> least some currently released distros (my idea originally) would be too much
> of a burden (especially considering Samba and Kerberos), and we can limit
> testing new features to the baseline of Fedora Rawhide (for which purpose I
> brought up a new Jenkins node).
>
> However, if we limit these only to (some) packages we "control" and know how
> to build properly for corresponding distros, then perhaps it will be
> manageable. Lukas, am I right that you already maintain a set of repos for
> ding-libs? We can still disable features which require other packages.
>
> Still, if we are to use that in CI, we'll have to fully commit to the
> maintenance of a repository holding these packages and will have to make it
> official: mention it in the developer instructions along with supported
> distros.
>
> Then, if we would like to use this repo to enable new features not only for
> mock builds, but for the native CI builds as well (benefiting test coverage,
> valgrind, clang scanner, etc. on older distros), we'll have to add
> instructions to add this repo to yum configuration, so CI could install the
> newer packages.

And we'll have to do this, if we're to continue pulling the dependency
information from the spec file.

Nick



More information about the sssd-devel mailing list