wput-devel Mailing List for wput
Brought to you by:
rumpeltux
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Alexander P. <ale...@gm...> - 2007-05-08 09:17:57
|
Hello, I've got few issues. 1. At http://wput.sourceforge.net/, section "Bleeding edge code from CVS", both strings should be updated: -cvs -d:pserver:ano...@cv...:/cvsroot/wput login -cvs -z3 -d:pserver:ano...@cv...:/cvsroot/wput co -P wput +cvs -d:pserver:ano...@wp...:/cvsroot/wput login +cvs -z3 -d:pserver:ano...@wp...:/cvsroot/wput co -P wput 1.5. Maybe some users don't know that anonymous user has an empty password. I would state that on the webpage. 2. Since you use autoconf, the Makefile should be removed from the CVS, since it is created as a part of a build process. Same about po/Makefile and src/Makefile. Just remove those files. 3. I would recommend to unzip the doc/wput.1.gz so that people could send patches to the manual as well. Thanks for the great tool! -- Alexander Pohoyda <ale...@gm...> PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44 |
From: Charles G. <cha...@un...> - 2005-08-24 16:43:34
|
Hagen, After much research I finally have an answer on OpenSSL incompatible license issue. In you are the copyright holder for all of wput, you can elect to put that exeption in a README file with the source. We would also have to distribute a OpenSSL license with the GPL one. This allows people to distribute binary files linked against the OpenSSL stuff. On Tue, Aug 23, 2005 at 04:30:32PM -0400, Dave Turner via RT wrote: > > [cha...@un... - Tue Jul 26 10:39:22 2005]: > > > > I help maintain wput, a command-line ftp-client that looks like wget > > but instead of downloading, uploads files or whole directories to > > remote ftp-servers (http://wput.sourceforge.net/). > > > > Our latest release candidate uses OpenSSL. Before we release it, we > > want to make sure we are following whatever legalities the FSF > > requires. Currently, the wput code under GPL and ships with a copy > > of "GNU GENERAL PUBLIC LICENSE", Version 2, June 1991. > > > > We may switch to using GNUTLS in the future but for now, we would > > like to be granted permission to distribute our code under a GPL > > with the following exeption added to our README file: > > > > "In addition, as a special exception, the Free Software Foundation > > gives permission to link the code of its release of wput with the > > OpenSSL project's "OpenSSL" library (or with modified versions of > > it that use the same license as the "OpenSSL" library), and > > distribute the linked executables. You must obey the GNU General > > Public License in all respects for all of the code used other than > > "OpenSSL". If you modify this file, you may extend this exception > > to your version of the file, but you are not obligated to do so. > > If you do not wish to do so, delete this exception statement from > > your version." > > > > I will also included a copy of the OpenSSL copyright licenses (dual > > license for OpenSSL and SSLeay). > > If you're the sole copyright holder (or have agreement from other > copyright holders), you can use that exception. If FSF is a copyright > holder, Richard Stallman <rm...@gn...> is the person to ask for > permission. He will probably ask that you use GNUTLS instead. > > -- > -Dave "Novalis" Turner > GPL Compliance Engineer > Free Software Foundation -- Charles Gagnon | My views are my views and they http://unixrealm.com | do not represent those of anybody charlesg at unixrealm.com | but me. Where do forest rangers go to get away from it all? -- Dennis Miller |
From: Hagen F. <ha...@it...> - 2005-07-23 12:20:52
|
wput-pre0.6 has been out a while and seems to be quite stable so far, but until the final 0.6 can be released there are still a few things to be done: o licensing issue: wput uses the openssl-library for the encryption, and this library has some strange licensing terms (as can be seen in wget for example where they include the additional permission to link the code with that library) So for wput the situation needs to be cleared, that means that we have to find out what exactly we need to include in the copyright notices and what needs to be done as well (such as asking for permission if necessary). The long term objective should be to move from the openssl-library to GnuTLS. o build-process: The build process is patchwork, so maybe this could be fixed / made more stable however. Esp. the locale-directory seems to be never determined correctly and i have quite a lack of experience with the configure/Makefile stuff. o translations: The translation to French and Swedish are still in progress, so they have to be awaited. o documentaion? Well, the documentation is there, but quite unhandy. Maybe instead of having these USAGE.* text files, we could make up a web-page explaining the usage, and additionally add some of the usage-information to the manpage. A FAQ wouldn't be wrong as well. That would be the most important things. Once they are done 0.6 is to be released and the work on future versions can begin. What about nightly (or at least weekly) automated builds from CVS. I suppose there is no way sf does this, so this has to be done remotely and the file would be listed on the homepage instead on the sf-release-listing for easier handling. |
From: Charles G. <cha...@un...> - 2005-07-22 18:59:45
|
Changing made sense but I couldn't really rename the old list so I just created a new and I'll delete the old one. -- Charles Gagnon | My views are my views and they http://unixrealm.com | do not represent those of anybody charlesg at unixrealm.com | but me. Why don't we just have a stupidity tax? Just tax the stupid people! |