Re: Splitting AppStream data into Workstation/Server

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, 2017-09-05 at 08:31 +0200, Nicolas Chauvet wrote:
> 2017-09-04 19:20 GMT+02:00 Richard Hughes <hughsient@xxxxxxxxx>:
> > On 4 September 2017 at 17:56, Neal Gompa <ngompa13@xxxxxxxxx>
> > wrote:
> > > It sounds like it would make more sense for createrepo_c to link
> > > to
> > > the AppStream builder library to handle AppStream metadata
> > > processing
> > > as part of the createrepo_c repodata generation, wouldn't it?
> > 
> > 100% agree. This does take some time currently (as we have to
> > decompress some files from the lzma archives) but this is currently
> > done using my AMD Athlon Neo Microserver with spinning rust drives.
> > Using something XEONy and SSDy it'd be orders of magnitude faster.
> > Are
> > we sure that we're using createrepo_c for composes? I know we
> > *used*
> > to be the old python one for some reason.
> 
> As I understand, the problem with the decompression is that it
> fetches
> the payload.
> And if a rpm weight 100MB, it will downloads (RPMs are often stored
> on
> nfs, so network is involved) and decompress the whole 100MB
> (including
> the header, although this last might be uncompressed).
> On the opposite, storing information on the RPM header means grabbing
> only the first KB out of the whole RPM.
It is in Provides, so it is in primary.xml of repodata. So it should be
very trivial to filter such RPMs and download only required ones.
> 
> As one can see, this might work for few RPMs, but this doesn't scale
> at all on a big whole repository with many arches, specially if the
> work from a previous appdata-builder run cannot be cached for a later
> updates.
> 
> So I wonder if it would be possible to have a "second payload" with
> only the appdata (xml, imgs) that it would be possible to fetch along
> the header without having to get the rest of the RPM ?
> On the second tough, with the effort needed to extract this
> information out of the rpm, is it really worth to store them there in
> the first step ? Over storing an URL (for xml and/or imgs) in the RPM
> header ?
That's probably something what openSUSE does, but I didn't really check
so better to ask Neal..
> 
> Thx for correcting me where I'm wrong.
> 
> -- 
> -
> 
> Nicolas (kwizart)
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

- -- 
- -Igor Gnatenko
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlmuRzAACgkQaVcUvRu8
X0zKyg//XnDPz5u1RC6jADUgnh2iZynRCWMKUuUmUvqk4a+6JQE5VkaomXpMs06H
Swn7F1OY2rGp52UYDbKy92vitfytH6T/SMIgGkqb0A0EOIYlMwDi4BTdUnq0LNkb
sm6lP0GNB4FFcChbKgY68frmBAxwZMwJlHthVkRBtjlMM1jKf/1WhK88gxEar7Lm
+a6b8X7mOXaFIFf5zAeik6g3XwAcrp0REGaG/m9is8sV/F7gea6vDI9MRFT4G1dz
dfGQxT8eYjBP8ldfWF21/7bUDjmLw6qAGvj8ni7mBHOwAXUfNv/dUDcCaJo19g3p
GtDdqBOKjN8BH1Rd/7E/aApfqR8AW9qphqDPd9Dz3gJVnZJegxQkHwsTdI45H5Ij
Hk8TmZL6qp5egNHWBKhOWy6CmbDB9ebPFDmJeJVe4m09rWQf7EmGyc1jL2XysXKF
gKSVsRA54E6iIDneN7KSqhB90lNMifPN4OsCLORbZANBGUggcYOaAwZKg3to/AiM
r0G2zLGN8n/oqFCxTvIfjZbPUEZr70vvK5L5zHxwl1W5cQzMyfJep8J6YbZtMuIs
jz9YhRdxG9kqInc2YT6lNoIhrp6NvhSbhd+nhQQCMo+LYKBrAIQ8bIKzrj00f92G
iRmoI9QnzdhXzvQQyz3v5WACcE1d5U4UuQnsFMWohrBjtWSrJVo=
=17U1
-----END PGP SIGNATURE-----
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux