<div dir="ltr">While my opinion probably doesn't mean much, I think we should be keeping memtest everywhere it is able to be used. We really need to update it to 5.01 for trusty though</div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Wed, Jan 22, 2014 at 1:01 AM, Colin Watson <span dir="ltr"><<a href="mailto:cjwatson@ubuntu.com" target="_blank">cjwatson@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Dec 10, 2013 at 11:39:44AM -0500, Scott Moser wrote:<br>
> On Tue, 10 Dec 2013, Colin Watson wrote:<br>
> > On Tue, Dec 10, 2013 at 10:35:40AM -0500, Scott Moser wrote:<br>
> > > On Tue, 10 Dec 2013, Colin Watson wrote:<br>
> > > > I think it's helpful for user-facing documentation for it to be<br>
> > > > consistently installed by default, especially since a system with memory<br>
> > > > integrity problems may have trouble installing packages; but I'd be<br>
> > > > happy for it to be moved out to desktop-common + server so that it<br>
> > ><br>
> > > well, cloud-image includes ubuntu-server, so I don't really want it there<br>
> > > either.<br>
> ><br>
> > It does? That's not reflected in its seed.<br>
><br>
> I believe you told me not to do that.<br>
> <a href="http://irclogs.ubuntu.com/2013/09/19/%23ubuntu-devel.html#t13:54" target="_blank">http://irclogs.ubuntu.com/2013/09/19/%23ubuntu-devel.html#t13:54</a><br>
> <a href="https://bugs.launchpad.net/ubuntu/+bug/1224504" target="_blank">https://bugs.launchpad.net/ubuntu/+bug/1224504</a><br>
> <a href="http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.saucy/revision/2164" target="_blank">http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.saucy/revision/2164</a><br>
<br>
Well, not quite. Here's the relevant bit of what I said in that IRC<br>
log:<br>
<br>
<cjwatson> smoser: That said, cloud-image looks substantively duplicated from server<br>
<cjwatson> smoser: So it does look as though that STRUCTURE change might be a mistake<br>
<cjwatson> smoser: Either that, or there's a load of stuff in cloud-image that should now be deleted because it's already in server<br>
<cjwatson> smoser: Either way, you should indeed make the image build process line up with the seed structure<br>
<cjwatson> smoser: And consider the future question of whether you might ever want something in the default server install but *not* in cloud images<br>
<br>
So what I told you was that you need to either:<br>
<br>
* have cloud-image inherit from server in STRUCTURE and not duplicate<br>
most of its contents<br>
<br>
*or*:<br>
<br>
* have cloud-image not inherit from server in STRUCTURE and duplicate<br>
most of its contents<br>
<br>
but not somewhere in between. You picked the latter option, which is<br>
fine by me.<br>
<br>
I think memtest86+ is a great example of something that we might want in<br>
the default server install but not in cloud images; so my favoured<br>
option here would be simply to move memtest86+ to the desktop-common and<br>
server seeds, which I believe will cause it to vanish from the cloud<br>
images as things are currently configured.<br>
<br>
And, after all, there are already other examples of packages that are in<br>
server and that make sense there, but that wouldn't make sense in cloud<br>
images: for example, ethtool.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Colin Watson [<a href="mailto:cjwatson@ubuntu.com">cjwatson@ubuntu.com</a>]<br>
<br>
--<br>
ubuntu-devel mailing list<br>
<a href="mailto:ubuntu-devel@lists.ubuntu.com">ubuntu-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br>
</font></span></blockquote></div><br></div>