Re: Packagers Guide Update #5

[Andreas Mohr]

On Thu, Jan 23, 2003 at 11:42:31PM -0500, Tom Wickline wrote:
> Changelog
>
> Update the Sample config

IMHO this doesn't even have *any* business in the Packaging Guide.
The guide should simply contain a pointer to the REAL sample config file,
otherwise this exactly leads to the permanent updating mess which you
just demonstrated ;-)

Packagers Guide Update #5

[Tom Wickline]

Andreas Mohr wrote:
> On Thu, Jan 23, 2003 at 11:42:31PM -0500, Tom Wickline wrote:
> > Changelog
> >
> > Update the Sample config
>
> IMHO this doesn't even have *any* business in the Packaging Guide.
> The guide should simply contain a pointer to the REAL sample config file,
> otherwise this exactly leads to the permanent updating mess which you
> just demonstrated ;-)

I am aware of this...
There was a Sample win.ini at the end of this list and I moved it
here. Now it is the Sample config file.... And put a Sample RH .spec in 
its place.

I looked at the config sample and it gets updated about once a month on 
average
but im trying to fill holes. = 
http://www.winehq.com/Docs/wine-pkg/pkg-wineconf.shtml

I'm not saying this is the best approach but at least it is upto date!
And when _you_ or anyone else has time we can tweak it ;-)

Flames, Comments, and most of all Volinteers and Patches are Welcome.

Tom

Packagers Guide Update #5

[Dan Kegel]

Tom Wickline wrote:
> > IMHO this doesn't even have *any* business in the Packaging Guide.
> > The guide should simply contain a pointer to the REAL sample config file ...
>
> I'm not saying this is the best approach but at least it is upto date!

How about writing a shell script or Makefile rule to
automatically insert the current config into the
doc when you're about to process it?
- Dan

Packagers Guide Update #5

[Tony Lambregts]

Dan Kegel wrote:
> Tom Wickline wrote:
> > > IMHO this doesn't even have *any* business in the Packaging Guide.
> > > The guide should simply contain a pointer to the REAL sample config 
> > > file ...
> >
> > I'm not saying this is the best approach but at least it is upto date!
>
> How about writing a shell script or Makefile rule to
> automatically insert the current config into the
> doc when you're about to process it?
> - Dan

I don't think it is nessasary for a configure or shell script for this. 
I think we can just include it. Declaring it as an entity and wraping it 
in <programlisting> _should_ work.

Tom:  you can try this your self or if you want/need some help with this 
I'll see what I can do.