[PATCH] run-pungi: atomic: Change the `ostree_osname` to be fedora-atomic

[Colin Walters]

On Tue, May 5, 2015, at 09:41 PM, Colin Walters wrote:
> On Tue, May 5, 2015, at 09:05 PM, Dennis Gilmore wrote:
> > 
> > traceability in being able to take that name and map it back to the image it 
> > was installed from.
> 
> Thanks!  I appreciate having a more explicit rationale.  
> 
> The way you say "map it back" implies that this is something a
> downstream user would do.  Do you see
> a similar situation with "mainline"?  Do you see this as being addressed
> by the `VARIANT` bits from
> https://fedoraproject.org/wiki/Packaging:Per-Product_Configuration
> ?

So likely we should pursue expressing the F23 for Atomic as some
sort of variant tag, which is the same way mainline does it.
That way we don't need to overload the OSTree "osname".

> Given the above, I can't imagine that many users are going to find the
> binding between the image and osname to be substantially more useful
> than "fedora"/"fedora-atomic"/"fedora-cloud-atomic" etc.
> 
> I am definitely willing to explore other options to address "traceability".
> 
> One thing to note is that of course every installed system will have
> /root/anaconda-ks.cfg, which has many advantages for this such as
> existing since approximately time began, applying to non-Atomic,
> distinguishing between Vagrant and non-Vagrant, etc.

And given all of the above, I would really appreciate re-consideration
of the patch.