Tom Wickline wrote:
Tony Lambregts wrote:
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.
Declaring the sample config as an entity is as easy as the following patch.
Index: wine-pkg.sgml =================================================================== RCS file: /home/wine/wine/documentation/wine-pkg.sgml,v retrieving revision 1.1 diff -u -r1.1 wine-pkg.sgml --- wine-pkg.sgml 19 Jan 2001 20:58:37 -0000 1.1 +++ wine-pkg.sgml 26 Jan 2003 18:02:24 -0000 @@ -5,8 +5,8 @@ %authors;
<!entity packaging SYSTEM "packaging.sgml"> +<!entity config SYSTEM "samples/config"> ]>
<book id="index">
-----
After making that change you can include the config file anywhere you like by using the directive &config;
Getting around the <wineconf> problem is another problem however. It looks to me that this wineconf could just as easily been surrounded by stars or braces or whatever since getting rid of the lines does not seem to have affected any of my programs. If this is the case then getting rid of <> and replacing them with something else is the (easiest) solution.
If we cannot replace the <> around wineconf the burning question for me is what is the directive to tell the make process ignore <wineconfig> Does anyone have an idea? Vincent...?