I'm curious to find some differeing opinions pro/con use of XML for
configuration files... also lookin to see if anyone can think of a C lib
already design'd to use XML config files without havin to recreate the
wheel and write original code... could really save me some time...
Res
I'm curious to find some differeing opinions pro/con use of XML for
configuration files... also lookin to see if anyone can think of a C lib
already design'd to use XML config files without havin to recreate the
wheel and write original code... could really save me some time...
Re
On Mon, Aug 28, 2000 at 06:47:59PM +0200, "Jürgen A. Erhard" wrote:
> >> INSTALL
>
> Josip> If it's generic, don't include it. If it explains only
> Josip> stuff about compiling from source, don't include it either.
>
> But beware... it might mention config stuff inside this (or
> dep
> >> NEWS
>
> Josip> If it's like other NEWS files I've seen, this is fine. If
> Josip> there's no upstream changelog, use this as it.
>
> I'd rather not "mv NEWS changelog" (if that's what you ment). I like
> the (GNU-Standard) NEWS/ChangeLog split, and I like to see NEWS as
> "NEWS
On Mon, Aug 28, 2000 at 06:47:59PM +0200, "Jürgen A. Erhard" wrote:
> >> INSTALL
>
> Josip> If it's generic, don't include it. If it explains only
> Josip> stuff about compiling from source, don't include it either.
>
> But beware... it might mention config stuff inside this (or
> de
> "Josip" == Josip Rodin <[EMAIL PROTECTED]> writes:
Josip> On Tue, Aug 22, 2000 at 11:07:29PM +0200, Hugo van der Merwe wrote:
>> Where does one draw the line about how much documentation should be
>> included? I just finished the first version of my first package, I threw
>>
> >> NEWS
>
> Josip> If it's like other NEWS files I've seen, this is fine. If
> Josip> there's no upstream changelog, use this as it.
>
> I'd rather not "mv NEWS changelog" (if that's what you ment). I like
> the (GNU-Standard) NEWS/ChangeLog split, and I like to see NEWS as
> "NEW
> "Josip" == Josip Rodin <[EMAIL PROTECTED]> writes:
Josip> On Tue, Aug 22, 2000 at 11:07:29PM +0200, Hugo van der Merwe wrote:
>> Where does one draw the line about how much documentation should be
>> included? I just finished the first version of my first package, I threw
>>
I believe some similar cases have been handled earlier by
suggests type dependencies. The reasoning is:
- the main functionality does not require wish, so it must
not be required
- recommends is also a bit heavy handed for this, the
package is perfectly usable without it (i.e. no
functionalit
I believe some similar cases have been handled earlier by
suggests type dependencies. The reasoning is:
- the main functionality does not require wish, so it must
not be required
- recommends is also a bit heavy handed for this, the
package is perfectly usable without it (i.e. no
functionali
10 matches
Mail list logo
