Thanks for the help, I should also mention I have some C++ , .Net, lots of Scripting experience. I also have pretty good problem solving skills. So I learned how to use automake... because I was tired of waiting for the buildbot :) And I like to watch the make process.
I also should mention that I have OCD when something doesn't work how I want it to work I lose sleep:) There should be no reason we can't get this UPS working, I got 2 of them for free, so I should be able to at least keep one of them for testing alone. If worst comes to worst, and there is something I am unable to do, I will hook up a box and give you root if you like. I have the new source, and will be posting the same stuff back. And thanks for bearing with me as well. On Sun, 2010-01-31 at 22:39 -0500, Charles Lepple wrote: > On Jan 31, 2010, at 9:11 PM, chance fulton wrote: > > > Sorry, I'm a noob at Linux development, do I need to uninstall > > before I > > make install the newer version. I was under the impression that it > > would > > overwrite the old binaries. > > Yup, it will. > > > My process is as follows. > > > > #svn co svn://svn.debian.org/nut/trunk nut > > #cd nut > > #autoreconf --install > > Oh, sorry I wasn't clearer about the instructions. You mentioned > something about being new at autoconf, and I thought you were still > using the tarballs from Buildbot. > > I realized that we were probably going to break a few things in the > process of getting this driver going, so I created a branch in SVN. > The new SVN URL for this is 'svn://svn.debian.org/nut/branches/ > tripplite-proto-3004'. Both that branch and the trunk have a revision > 2300, but the changes don't show up on the trunk (until we merge them > back in later). This makes it easier for me to do regression testing > on the UPS I have here (since I can compare the trunk to the branch). > > No need to blow away your checked-out copy of the trunk - just run 'cd > nut', then 'svn switch svn://svn.debian.org/nut/branches/tripplite- > proto-3004' (only needs to be done once; the current SVN URL is stored > in the working copy, as shown by 'svn info'). > > Then, after I check in something new, you can just run 'svn up' in > that same directory, and it will just pull the changes (rather than > downloading the whole thing). > > Another advantage of SVN is if you make a change to the code on your > end, you can run 'svn diff' and send the resulting patch back. > > > #./configure --with-user=nut --with-group=nut --with-usb > > This looks correct. > > Thanks for bearing with me. > _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
