Hi,
On 01/17/2012 11:54 PM, Richard W.M. Jones wrote:
On Tue, Jan 17, 2012 at 11:05:36PM +0100, Hans de Goede wrote:
Once that is done, then just adding the vala bindings to the
devel-package likely takes less disk space for those who
do install them, then the meta data needed for a separate subpackage,
and that metadata needs to be downloaded and *stored* by all users,
not just those installing the -devel package.
You've measured this, right?
I just ran some tests for you, here you go
spice-gtk3-devel.rpm size with vala bindings included:
10865
spice-gtk3-devel.rpm size without vala bindings:
9921
Compressed size of bindings files:
10865 - 9921 = 944 bytes
spice-gtk3-vala.rpm (separate vala bindings pkg):
7645
Separate pkg header size / overhead:
7645 - 944 = 6701 bytes
Installed vala bindings size:
2808 bytes (in 2 files).
So either we are forcing *all* our users to download
and store say 3k of extra metadata (assuming yum metadata
is more efficient then rpm headers), or we are forcing
those who install -devel packages to install 2808
bytes extra under /usr/share/vala/vapi
I'd like to see hard figures
before we dismiss the idea of packaging this correctly.
Splitting packages is not always about doing things
"correctly" splitting packages has a cost, in the form
of added metadata, and through that more bandwidth and
disk usage and slower yum performance, for *all* of our
users not just the users of the package in question!
So we need to find a balance between splitting packages
where necessary and not splitting them up unnecessarily.
Also we are talking about -devel packages here which
typically have tons of deps anyways and are typically
installed on bigger machines rather then smaller ones.
I'm not saying that -devel packages can be any size,
and can freely drag in whatever deps. But splitting
off the vala bindings just because of their puny
file size is counter productive.
So back to the issue at hand, to me the bigger problem
is the ownership of the /usr/share/vala/vapi directory,
if we can come up with a solution for that, then I think
it is safe to say that vala's vapi files should be part
of a package's -devel subpackage (as is the case atm
for all but 2 packages on my system).
Regards,
Hans
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
