Jeff Spaleta wrote:
2008/8/19 Karsten 'quaid' Wade <kwade@xxxxxxxxxx>:
Owners stats:
- 6517 packages
- 10799 binary rpms in devel
Darn, I was afraid of that. We are all perfectly aware that one package
(tarball + spec file) can yield more than one binary rpm.
Would it be better to consistently start using a term like component
or module to indicate the tarball+spec+patchset entity...especially
since people are vectoring towards making it possible to work with
explode sources in our buildsystem without generating an srpm
'package' at all.
Yes those people may or may not be smoking crack.. but they appear to
be pretty serious about making it possible to work with some sort of
exploded tree as an option to srpms for some of the components we
maintain...can't really call an exploded tree a package.
Or, instead of having a subtle name change for each subtle stage change
in turning foo into baz via bar, we could just stick with 'package' and
suggest that a 'package' is something you can yum install or
yumdownloader --source.
-Jeroen
--
Fedora-marketing-list mailing list
Fedora-marketing-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-marketing-list
