Re: [OT] Configuration file parsing
At 2004-01-13T19:26:34Z, "Ph. Schulz" <[EMAIL PROTECTED]> writes: > Somebody said that I would be fine (when using GPL-licensed stuff) as long > as I provide the sources to people who use the application. I guess > providing the source within the company is not a problem... No. Again, no. An entity does not have to make source available unless it distributes the product to another entity. You can build proprietary software using GPL components as long as you do not distribute *outside your company*. If it stays internal, you have no legal or moral obligation to make your source available. Yes, using BSD libraries avoids the problem, but the GPL isn't as restrictive as you're making it sound. -- Kirk Strauser "94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box." pgp0.pgp Description: PGP signature
Re: [OT] Configuration file parsing
Thank you all for your input, I really appreciate it. Somebody said that I would be fine (when using GPL-licensed stuff) as long as I provide the sources to people who use the application. I guess providing the source within the company is not a problem, however I thought it would be easier to use BSD-style licensed stuff. Thanks again, Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] Configuration file parsing
On Jan 12, 2004, at 5:45 AM, Philip Schulz wrote: I'm currently working on a program which will be used in a closed company environment. The programm is written in C. For this program, I need to find a way of parsing a configuration file. I found a library which can do exactly what I need, it's GLib's lexical scanner [1]. What are your requirements for this configuation file? Something that deals with "classic" Unix config files (ie, along the lines of /etc/rc.conf and the like), with #-style comments and simple key-value assignment should only take a few hours to whip up, if you can't use GLib or other GPL'ed code for your circumstances. If you need something fancier, consider lex and yacc (or flex & bison), but XML property lists are another alternative that might be more flexible. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] Configuration file parsing
At 2004-01-12T11:21:02Z, "Rob" <[EMAIL PROTECTED]> writes: > As far as I understand it, the main requirement of the GPL is that you > make the source available to the same people that use the binaries. So if > your program was never released outside the company, an internal FTP > server hosting the source should be sufficent. That's not even necessary. If you're not distributing it outside the company, then you're not obligated to provide source to people within the company. -- Kirk Strauser "94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box." pgp0.pgp Description: PGP signature
Re: [OT] Configuration file parsing
Philip Schulz wrote on Monday January 12, 2004: > I'm currently working on a program which will be used in a closed company > environment. The programm is written in C. For this program, I need to find > a > way of parsing a configuration file. I found a library which can do exactly > what I need, it's GLib's lexical scanner [1]. However, it's licensed under > the > GPL, so I guess it won't work for me. As far as I understand it, the main requirement of the GPL is that you make the source available to the same people that use the binaries. So if your program was never released outside the company, an internal FTP server hosting the source should be sufficent. Are there other aspects of the GPL that make it unsuitable for your project? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] Configuration file parsing
On Mon, Jan 12, 2004 at 11:45:25AM +0100, Philip Schulz wrote: > Hello! > > Let me apologize for asking an offtopic question. If you feel offended, > please ignore this eMail. > > I'm currently working on a program which will be used in a closed company > environment. The programm is written in C. For this program, I need to find > a > way of parsing a configuration file. I found a library which can do exactly > what I need, it's GLib's lexical scanner [1]. However, it's licensed under > the > GPL, so I guess it won't work for me. > So my question: How can I easily parse a configuration file? Any pointers > appreciated. Guess for windows ini files, you could use: http://freshmeat.net/projects/inifileparser/ Gautam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"