[Rpm-ecosystem] Boolean dependencies vs self-provides (for rust "features" support)

[Igor Gnatenko]

On Mon, 2017-01-30 at 10:46 +0100, Michael Schroeder wrote:
> On Sun, Jan 29, 2017 at 05:33:34PM +0100, Igor Gnatenko wrote:
> > But it doesn't work since it works the RPM thinks that
> > crate(clap)(xxx)
> > is going to be installed (since it's provided by same package) so
> > it
> > requires other packages to be installed as well which is something
> > not
> > what we want.
> > 
> > Probably for now sane way would be just require all optional
> > packages
> > to cover *all* features which package provides, but it means that
> > builds will be slow because they would need to pull a lot of
> > packages
> > always.
> 
> Seems like you want devel packages for each feature:
That would mean that if upstream removes one of features we can't
update it in stable release without proper obsoletes. But since I want
to generate all this stuff automatically it's not possible...
> 
> crate-clap-color-devel:
>   Provides: crate(clap)(color)
>   Requires: crate(clap) crate(ansi_term) crate(libc)
> 
> Cheers,
>   Michael.
> 
-- 
-Igor Gnatenko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.rpm.org/pipermail/rpm-ecosystem/attachments/20170130/566ab7f1/attachment.asc>