<div dir="ltr">0.9.x build is available on fedorapeople [1], which works fine (i am running it on fedora 19). I tried building the rpm with 1.0.0, but the stock rpm spec (or the templates) has some mounting issues, i could not get it working properly (all the lxcs rootfs points to host system with all privileges :-( ). i didnt get time to debug it...<br>
<br>[1]<a href="http://thm.fedorapeople.org/lxc/">http://thm.fedorapeople.org/lxc/</a><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 16, 2013 at 11:30 AM, Dwight Engen <span dir="ltr"><<a href="mailto:dwight.engen@oracle.com" target="_blank">dwight.engen@oracle.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 16 Dec 2013 09:52:22 -0500<br>
"Michael H. Warfield" <mhw@WittsEnd.com> wrote:<br>
<br>
> Ok...<br>
><br>
> So I work on a lot of RHEL / CentOS / Fedora / SL / NST stuff.<br>
> Basically they're all rpm based systems. I generally test through the<br>
> rpms. i.e. I don't build from scratch, scratch, I rebuild rpm's for<br>
> myself and install from yum each time. It actually makes things<br>
> easier and, occasionally, I spot something that I realize is wrong<br>
> that wouldn't show up otherwise...<br>
><br>
> I've been puzzling about something and I think now that the<br>
> <a href="http://lxc.spec.in" target="_blank">lxc.spec.in</a> file needs some loving care and updating. What I noticed<br>
> was that a number of posts refer to "lxc-ls --fancy" but my version<br>
> of lxc-ls is a bash script and doesn't have that option. That's from<br>
> src/lxc/legacy. There's the python script lxc-ls but that's not<br>
> getting installed in the rpm by the spec file. Installing by hand,<br>
> the Python lxc-ls gives me "python: lxc module not found" or some<br>
> such.<br>
<br>
Hi Mike, I also almost always just build an rpm and install it. The python<br>
stuff doesn't get built on Oracle Linux 6.5 (so I suspect it will be<br>
the same for RHEL, CentOS, SL etc., but not Fedora) because there is no<br>
python3 available, which is why the legacy lxc-ls gets included there.<br>
I'd think configure would get the newer stuff built on Fedora, but maybe<br>
the .spec isn't packaging it?<br>
<br>
> Crap. That means the spec file has not been updated for all this API<br>
> stuff that's been going on and I'm not sure what needs to be updated<br>
> in there. I'd like to look at making those changes and bringing that<br>
> up to date ASAP before we go Beta (priority over a couple of other<br>
> putter projects) but I'd like some guidance over what's needed. I<br>
> fear it's more than just getting lxc-ls to the latest and greatest...<br>
<br>
I think it does make sense to update the .spec file and split out<br>
python into a separate pkg like the lua stuff is.<br>
<br>
> Regards,<br>
> Mike<br>
<br>
_______________________________________________<br>
lxc-devel mailing list<br>
<a href="mailto:lxc-devel@lists.linuxcontainers.org">lxc-devel@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-devel" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-devel</a><br>
</blockquote></div><br></div>