> 1. you have upstreams from hell like TeXLive that bundle many many unrelated
> parts of the same kind.
So you need some way to tell rpm "autocreate subpackages but split them around
those fileset lines"
Sure. And even in Solus' packaging mechanism, the user can override automatic
pattern matching to do their own patterns.
> 2. you still need to declare package summary and description somewhere (not
> all descriptions can be autocomputed)
Absolutely, and they can be manually specified as needed. That being said, in a
large number of cases, it isn't necessary to do so.
Think for example how we package Python modules in Fedora. The summary and
description is basically repeated with an additional statement on which version
of Python it targets based on the flavor.
In my view, implementing this feature would make things like proper
multilibbing automatic, as well as doing libs/devel splits automatically,
Python package flavor splits, Ruby flavor splits, and so on.
Yes, there are exceptions: TeXLive and the Linux kernel are probably not going
to benefit much from this, for example. But this is a _huge_ improvement for
the overwhelming majority of cases.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/329#issuecomment-350498104
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
