#5984: Adding metadata to the Fedora Workstation Live CD

[Fedora Release Engineering]

#5984: Adding metadata to the Fedora Workstation Live CD
----------------------------+------------------------
 Reporter:  rhughes         |       Owner:  rel-eng@…
     Type:  task            |      Status:  new
Milestone:  Fedora 21 Beta  |   Component:  koji
 Keywords:                  |  Blocked By:
 Blocking:                  |
----------------------------+------------------------
 Hi Dennis, and other rel-eng dudes!

 I've hit somewhat of a roadblock with this:
 http://blogs.gnome.org/hughsie/2014/08/29/putting-packagekit-metadata-on-
 the-fedora-livecd/

 Basically, I need access to the post-mash (i.e. fedora, fedora-updates)
 from the compose server. This allows us to put the old metadata on the
 Fedora LiveCD so we don't have to wait the few minutes after install to be
 able to search for and install new applications.

 I totally agree we don't want unfettered internet access, or even access
 to the mirror network, as I'm happy doing something like this in the
 fedora-live-workstation.ks file:

 %post --nochroot
 DESTDIR=$INSTALL_ROOT $INSTALL_ROOT/usr/libexec/packagekit-direct refresh
 --rewrite-baseurl fedora=http://some.local.ip.address/f21  --rewrite-
 baseurl updates=http://some.local.ip.address/f21-updates

 On the assumption that some.local.ip.address is available from inside the
 LiveCD builder and gives us access to the mash'ed *metadata* only (I don't
 need packages, and it can even be a few days old with no penalty).

 The alternative is that I ship the fedora and updates metadata in the
 PackageKit rpm file, which means doing a -0.01 day release of the RPM for
 the Live media, which makes everything so very fragile.

 Other ideas of course welcome. Thanks!

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5984>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project