Corrent. I suggest new subdirectory here: http://openhpi.svn.sourceforge.net/viewvc/openhpi/
At the same level as openhpi, hpiview, hpiview2, subagent. Anton Pak > Anton - > > That sounds good. So in this proposed organization, the HPI GUI app > source would not even be in the main openhpi development tree. Is that > right? > > --michael > > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> Sent: Thursday, May 27, 2010 3:16 PM >> To: [email protected] >> Subject: Re: [Openhpi-devel] HPI GUI application proposal >> >> >> My proposal is to organize it in the same way as for existing >> hpiview or >> pyOpenHPI: >> - openhpi and hpiview are in the same SVN repo. (not sure >> about the same) >> - separate tarball hpiview-$version.tar.gz >> >> Anton Pak >> >> > Anton - >> > >> > Perhaps I'm getting ahead of myself here - but it sounds >> like the HPI GUI >> > app source code could be included in the OpenHPI project - >> but that the >> > user would be responsible for downloading the QT4 >> development/runtime kit >> > prior to building it? If this is what you are envisioning, >> then the HPI >> > GUI app would have to have its own separate build target in >> the OpenHPI >> > makefile - so that user can still build the rest of the >> OpenHPI (including >> > the clients) without having the QT4 stuff present. I would >> not want to >> > require/force users to load the QT4 stuff if they don't >> care about using >> > the new HPI GUI app. >> > >> > So the only dependency on QT4, in the above description, is >> the HPI GUI >> > app you are proposing. Is that how you see it going? My >> desire here is >> > for not adding new header file/code dependencies in the >> build chain for >> > stuff that is already working. In other words, I should >> still be able to >> > build the existing OpenHPI and clients without having QT4 present. >> > >> > --michael >> > >> > >> > >> >> -----Original Message----- >> >> From: [email protected] [mailto:[email protected]] >> >> Sent: Thursday, May 27, 2010 2:47 PM >> >> To: [email protected] >> >> Cc: '[email protected]' >> >> Subject: Re: [Openhpi-devel] HPI GUI application proposal >> >> >> >> >> >> Michael, >> >> >> >> Yes, it requires QT4. >> >> Yes, one need to have Qt4 for compilation (like glib or >> >> openssl for OpenHPI). >> >> Dan pointed out there is no problem with BSD app and GPL lib. >> >> >> >> > Anton - >> >> > >> >> > I'm assuming the HPI GUI application you are proposing >> >> requires the QT4 >> >> > libraries to compile/run. Is that right? >> >> > If QT4 is LGPL2/GPL3 - isn't that going to cause issues if >> >> we include >> >> > those libraries with OpenHPI - given that OpenHPI is BSD? >> >> I think it >> >> > would be an issue. >> >> > >> >> > Or is your thinking: We include the GUI application source >> >> code in the >> >> > OpenHPI project - but in order for it to compile - the use >> >> must first >> >> > download the QT4 libraries? In other words, we include the >> >> HPI GUI - but >> >> > not the QT4 libraries - in the OpenHPI project? >> >> > >> >> > --michael >> >> > >> >> > >> >> > >> >> >> -----Original Message----- >> >> >> From: [email protected] >> [mailto:[email protected]] >> >> >> Sent: Thursday, May 27, 2010 2:27 PM >> >> >> To: [email protected] >> >> >> Subject: Re: [Openhpi-devel] HPI GUI application proposal >> >> >> >> >> >> >> >> >> Great! BSD license works! >> >> >> >> >> >> Anton Pak >> >> >> >> >> >> > [email protected] pÃÅ¡e v ÄŒt 27. 05. 2010 v >> >> >> 16:03 -0400: >> >> >> >> 1. We are fine with BSD license and PPS copyright note in the >> >> >> >> source files. In the same fashion like in OpenHPI >> source code. >> >> >> >> However QT4 is LGPL2/GPL3 and I read there were >> incompatibility >> >> >> >> issues with the original BSD license. >> >> >> >> Do you have any thougth on this topic? >> >> >> > >> >> >> > I think these URLs can help >> >> >> > http://tinyurl.com/34p65yc >> >> >> > https://fedoraproject.org/wiki/Licensing/FAQ >> >> >> > https://fedoraproject.org/wiki/Licensing >> >> >> > >> >> >> > >> >> >> > Dan >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> -------------------------------------------------------------- >> >> >> ---------------- >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Openhpi-devel mailing list >> >> >> > [email protected] >> >> >> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> -------------------------------------------------------------- >> >> >> ---------------- >> >> >> >> >> >> _______________________________________________ >> >> >> Openhpi-devel mailing list >> >> >> [email protected] >> >> >> https://lists.sourceforge.net/lists/listinfo/openhpi-devel >> >> >> >> >> > >> >> > >> >> -------------------------------------------------------------- >> >> ---------------- >> >> > >> >> > _______________________________________________ >> >> > Openhpi-devel mailing list >> >> > [email protected] >> >> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel >> >> > >> >> >> >> >> >> >> >> -------------------------------------------------------------- >> >> ---------------- >> >> >> >> _______________________________________________ >> >> Openhpi-devel mailing list >> >> [email protected] >> >> https://lists.sourceforge.net/lists/listinfo/openhpi-devel >> >> >> > >> > >> -------------------------------------------------------------- >> ---------------- >> > >> > _______________________________________________ >> > Openhpi-devel mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel >> > >> >> >> >> -------------------------------------------------------------- >> ---------------- >> >> _______________________________________________ >> Openhpi-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/openhpi-devel >> > > ------------------------------------------------------------------------------ > > _______________________________________________ > Openhpi-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > ------------------------------------------------------------------------------ _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
