I would be wary if you are running make install, I used to run that on my debian package and found that a few files were being installed on root.
Thank you for your time, -Chase ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On May 25, 2018 5:44 PM, Ulrich Wilkens <m...@uwilkens.de> wrote: > > > On 05/25/18 20:56, Matthew R. Trower wrote: > > > > I agree! > > > > > > > > > > > > > I sure wish there was some sort of CI in SourceForge > > > > Now that SourceForge has WebHooks, this should be possible: > > https://sourceforge.net/blog/how-to-use-webhooks-for-git-mercurial-and-svn-repositories/ > > > > It's still not something that SourceForge provides out of the box, but the > > tools are available for us to build something. > > > > > I have patches against all these problems. But they need some more tests > > > > > > before I can send them. I have ~40 Virtualbox test systems and some of > > > > > > them have to be tested twice due to different compilers. These tests > > > > > > are important because I often find new errors > > > > It's great to hear that you're doing this testing. Can you tell me more > > about your process, such as: > > > > - Do you use any automation, or is it a fully manual process? > > I'm doing most tasks automatically. If I did it manually I would be much > > older than now. :-) > > I'm doing it with simple self-written perl and shell scripts. They are > > located on a server system. > > The server has access to all test systems via ssh without password. It > > can start all necessary tasks > > and can collect the results and log files. > > The main effort is not the testing, it can run over night. Main effort > > is holding the test systems up to date. > > I'm doing it manually now and I'm searching for a better solution. > > > - Do you just check that make World succeeds, or do you do interactive > > testing (run/use the programs in some way) > > No, I'm doing a make World and also a make install and I'm checking the > > log files of both. > > If necessary I also start CDE, but only on relevant systems, since I've > > to do this step manually. > > > - Is the bulk of your time spent in the testing process, or in fixing > > problems that you find? > > Well, that depends. You can never know how difficult it is to find a fix > > and how many time you need. > > > Maybe there's some way I can assist you. I probably can't dedicate much > > time to fixing code, but I can offer compute resources / run build tests, > > in VMs, on metal, or both. > > > > > > > > Check out the vibrant tech community on one of the world's most > > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > cdesktopenv-devel mailing list > > > > cdesktopenv-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel > > Best Regards, Ulrich > > > ------------------------ > > Ulrich Wilkens > > Email: m...@uwilkens.de > > > ------------------------------------------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > cdesktopenv-devel mailing list > > cdesktopenv-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
