To make the serial api usable the ebuild has to create the directory: /var/lock/uucp and make it writable to the uucp group. Otherwise SI Prog I/O has to be used and this is only available to root as it is direct I/O on the serial addresses. With SI Prog API a user in group uucp has the rights make use of this.
thanks for the bug. I just emailed the author so that I can put in 2.06f as well (can't find the file). I'll correct this bug at the same time.
(In reply to comment #1) > thanks for the bug. I just emailed the author so that I can put in 2.06f as > well (can't find the file). I'll correct this bug at the same time. It seems the last available version for Linux is 2.06c. The website hasn't seen any activity for more than a year, now. Daniel (Black), have you received any answer from the author ? I'm concerned about the license, as our ebuild says LGPL-2, but somewhere on the website he says that the last release with a GPL license is 1.17 (didn't he mean LGPL instead ?). The binary-only versions surely can't be GPL or LGPL. If he doesn't answer your request, I'm afraid we'll have to punt the 2.x versions and go back to 1.17. I will try and send a message on the ponyprog forums, ans it seems the author still reads them. Denis.
> Daniel (Black), have you received any answer from the author ? The answer I got was: Hi Daniel, as stated on my site I had problem building the V library and Ponyprog with modern gcc (v3). However if I solve it, or find an old gcc to rebuild version 2.06f I will email to you. Cheers, Claudio Lanconelli > I'm concerned > about the license, as our ebuild says LGPL-2, but somewhere on the website he > says that the last release with a GPL license is 1.17 However there is no license mentioned for the later version and the top of the web page says ponyprog is GPL2. > (didn't he mean LGPL > instead ?). Maybe. I think the LGPL comes from the included V library. The license in the ebuild should reflect both. > The binary-only versions surely can't be GPL or LGPL. Well noticed. > If he doesn't > answer your request, I'm afraid we'll have to punt the 2.x versions and go back > to 1.17. Its the authors obligation to provide the source rather than Gentoo. I wouldn't jump to the conclusion to punt it because the author hasn't released the source under the license that they selected. > I will try and send a message on the ponyprog forums, ans it seems the author > still reads them. Good idea. The email response that I got was relatively quick.
(In reply to comment #3) > Its the authors obligation to provide the source rather than Gentoo. I wouldn't > jump to the conclusion to punt it because the author hasn't released the source > under the license that they selected. Don't we have a legal obligation of mirroring all the code or is it only for LiveCDs ? I seem to remember we have to do it for all open source apps we provide an ebuild for. In which case we may be as liable as the author if we both claim the app is GPL. I'll ask one of our legal Gentoo expert. > > I will try and send a message on the ponyprog forums, ans it seems the author > > still reads them. The author answered my question at http://ponyprog1.sourceforge.net/phorum/read.php?2,100 The source code for 2.06e is available in CVS and appears to have been committed 2 years ago. I did check last time and can't recall seeing this, although it's fairly possible I missed it. However I suppose that since you were looking for the code too, you would have looked for it in CVS too, and found it. Did you? Anyway, when I'll find some time, I'll make a CVS snapshot of version 2.06e and write an ebuild using that source code. Denis.
I have just committed an ebuild for ponyprog-2.07a that builds from source and should fix this bug. Thanks for reporting this. Denis.
