On Wed, Feb 28, 2018, at 9:43 AM, Dennis Gilmore wrote:
I think its better and more in the spirit of ostree to have a single repo for delivery
I agree! But...it also seems OK to have them be separate. The fact that one *can* rebase between the two is IMO very cool, but it's also not a common use case. (Having them be merged does highlight ostree's dedup, but I don't think we're hurting for storage space that much)
That said as you all (hopefully) know I am heads down on obsoleting this via https://github.com/projectatomic/rpm-ostree/issues/1081
So let's not try to do spend a significant amount of time engineering this; if merging them is easier, that's cool! If not, that's OK too by me. I'd really like to focus on productizing the rojig model, including details like how we maintain the history via RPMs.