<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Jun 19, 2019, at 14:55, Karanbir Singh wrote:<br></div><blockquote type="cite" id="qt"><div>On 19/06/2019 20:14, Brian Stinson wrote:<br></div><div>> <br></div><div>> Operationally, this means we'd compose BaseOS by itself at a<br></div><div>> point-release time, hard-link that tree over to the 'kickstart'<br></div><div>> location on the masters, and then re-spin for 0-day updates.<br></div><div><br></div><div><br></div><div>I was thinking we may just need a createrepo run somewhere else while<br></div><div>the baseos does not have 0+day updates etc. I dont know if we need to<br></div><div>hardlink content around etc.<br></div><div><br></div><div>Thinking one step out, would this metadata be the same as what we ship<br></div><div>on the ISO media ?<br></div><div><br></div><div>regards<br></div></blockquote><div><br></div><div>I'm trying to get us away from one-off processes done by hand. It's easier to copy the structure as-is after a GA compose, and run an update compose with all of updates directly afterward.<br></div><div><br></div><div>We could (and probably should) generate the install media from the GA compose.<br></div><div><br></div><div><br></div></body></html>