I never thought of the "install more than once" scenario, sorry about that. I suppose we could install RELEASE-VERSION in some FHS approved place, and update the search paths to include it. I will take a look at it today, hopefully.
On Fri, Nov 8, 2013 at 5:50 PM, Don Zickus <[email protected]> wrote: > (switch to autotest mailing list) > > On Tue, Nov 05, 2013 at 01:00:15AM -0200, Lucas Meneghel Rodrigues wrote: > > On 11/05/2013 12:00 AM, Nick Coghlan wrote: > > >On 11/05/2013 07:51 AM, Don Zickus wrote: > > >>On Tue, Oct 29, 2013 at 01:33:33PM +1000, Nick Coghlan wrote: > > >>>Ping :) > > >>> > > >>>Even a cursory blog post somewhere (or a reply to this email!) > > >>>explaining to people how to *experiment* with this would be helpful. > At > > >>>the moment I'm having to point people at the merged pull request to > say > > >>>"Yes, in theory, you can use the upcoming version of autotest as a > > >>>Beaker test harness", but I have zero resources to give them on how to > > >>>actually run it (because I don't actually know myself). > > >> > > >>So playing with things a little more.. > > Lucas, > > I am being bit by autotest/RELEASE-VERSION. > > python setup.py build > python setup.py install > > works great the first time round. > > Then once autotest is install in > /usr/lib/python2.7/site-packages/autotest/ > > doing the above commands again to install new changes fails because > autotest/setup.py::run() -> version=version.get_version() can't find > RELEASE-VERSION. > > I have to manually copy it to the install directory. :-( I tried hacking > up something in setup.py to copy it over during install, but did not have > much luck. Thoughts? > > Cheers, > Don > > _______________________________________________ > Autotest-kernel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/autotest-kernel > -- Lucas
_______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
