RFU: nasm-2.10.05-1
Upstream release, please upload. wget -x -nH --cut-dirs=2 \ http://scarff.id.au/file/cygwin/nasm/nasm-2.10.05-1-src.tar.bz2 \ http://scarff.id.au/file/cygwin/nasm/nasm-2.10.05-1.tar.bz2 Versions prior to 2.08.02-1 can be removed. This has been the first nasm update for me in a while - there have been two major releases upstream that I missed, and I was only prompted into updating the package by a direct email from a user who depended on the newer versions. While I'm happy to keep maintaining the Cygwin nasm package, I wouldn't object to someone else taking it over. :) -- Dean
RFU: nasm-2.08.02-1
Upstream release, please upload. wget -x -nH --cut-dirs=2 \ http://scarff.id.au/file/cygwin/nasm/nasm-2.08.02-1-src.tar.bz2 \ http://scarff.id.au/file/cygwin/nasm/nasm-2.08.02-1.tar.bz2 Thanks. -- Dean http://scarff.id.au/ -- software bugs and workarounds
Re: [RFU 1.7] nasm-2.06-1
Dave Korn wrote: [...] - should setup.hint have requires: cygwin? nasm's does. No, that's now an obsolete practice, it should be removed. See e.g.: http://cygwin.com/ml/cygwin-apps/2009-06/msg00145.html In that case: http://scarff.id.au/file/cygwin/nasm/setup.hint - should it be /usr/share/doc/nasm or /usr/share/doc/nasm-2.06? nasm's is the former Every package seems to have its own idea how to name the doc dir. It's not *that* important. I guess the better approach is to omit the version. After all, you usually have just one of the packages installed and the user doesn't exactly care for the actual version of the package when looking for the docs. Omitting the version number is the new convention; see the thread: [RFC] 1.7 Packaging: Documentation: http://www.cygwin.com/ml/cygwin-apps/2008-08/threads.html#00081 Thanks for the references, guess I didn't search hard enough. ;) Not sure whether there's a setup2.html in reserve, but when the time comes, I've attached a patch for setup.html for these two issues. --- setup.html 2009-07-01 23:41:51.0 +0800 +++ setup2.html 2009-07-01 23:43:57.0 +0800 @@ -257,7 +257,6 @@ /pre pThe above would place a package in a single category called ASCII Games rather than two categories ASCII and Games./p pThe ttrequires/tt line indicates the packages that this package relies on. If your package is dependent on a file provided by another package that other package should be included here. The requires field may be missing or empty if your package truly does not require any other package./p - pA package will probably require the ttCygwin/tt package if it contain any DLLs or executable files since the ttCygwin/tt package contains ttcygwin1.dll/tt, which is required for most programs. However, the ttCygwin/tt package would not be a required dependency for a package which contained only text files, as is the case with, for example, packages that consist entirely of man pages./p pA package can rely on multiple other packages. Hierarchical dependencies should work correctly, however, it is best to always include specific dependencies, i.e. don't drop 'ttbar/tt' from your dependency list if your package requires it, even if you are including 'ttfoo/tt' which relies on 'ttbar/tt'./p pConversely, do not include package dependencies of emdependent/em packages in your dependency list. If you think that another package has an incorrect dependency list, send email to cygwin-apps noting that fact./p pMultiple packages are separated by spaces. Do not enclose multiple package names within quotation marks./p @@ -355,7 +354,7 @@ liAll executables in your binary package are stripped (run 'strip' on them). Some makefiles have a install-strip command you can use to do this automatically when you setup your 'installed' tree. /li liSource packages are extracted in /usr/src. See the a href=#srcpackage_contentsPackage Source/a section for more information. /li liIn your binary package, include a file /usr/share/doc/Cygwin/foo-vendor-suffix.README containing (at a minimum) the information needed for an end user to recreate the package. This includes CFLAGS settings, configure parameters, etc. /li - liIn your binary package include a directory /usr/share/doc/foo-vendor/ that includes any binary-relevant vendor documentation, such as ChangeLog's, copyright licence's, README's etc. /li + liIn your binary package include a directory /usr/share/doc/foo/ that includes any binary-relevant vendor documentation, such as ChangeLog's, copyright licence's, README's etc. /li liIf you are not creating your package from an installed virtual root, be sure to check that the file permissions are appropriate. /li liIf the package has any global settings (ie in files in /etc) that are not overrideable on a per user basis (sshd, as a daemon, is an example of this) do not include the relevant config files in your package. Instead include in your post-install script to install the settings files. Be sure that if you would overwrite an already present file that the user is offered the choice of keeping their own or overwriting with your defaults. /li liEnsure that your package handles binary only systems, textmode only systems, and hybrid systems correctly. /li -- Dean
[RFU 1.7] nasm-2.06-1
Upstream release. Built for cygwin 1.7. There are a couple of relevant packaging conventions that I've noticed discussed on this list and in practice that contradict http://cygwin.com/setup.html yet haven't had an official response (at least I can't find it in the archives). - should setup.hint have requires: cygwin? nasm's does. - should it be /usr/share/doc/nasm or /usr/share/doc/nasm-2.06? nasm's is the former I forgot to announce the 2.05-1 package so I'll just announce this one once it hits the mirrors, assuming above issues aren't a problem. wget \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.06-1-src.tar.bz2' \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.06-1.tar.bz2' rm -f nasm-2.05-1-src.tar.bz2 nasm-2.05-1.tar.bz2 -- Dean
[RFU 1.7] nasm-2.05-1
Upstream release (actually I've missed a couple of minor upstream releases since the last cygwin package). Built for cygwin 1.7. wget \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.05-1-src.tar.bz2' \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.05-1.tar.bz2' rm -f nasm-2.01-1-src.tar.bz2 nasm-2.01-1.tar.bz2 Please upload :) -- Dean
Re: Please upload: nasm-2.02-1
On 26 Feb 2008, at 17:53 , Corinna Vinschen wrote: On Feb 26 11:43, Dean Scarff wrote: Upstream release. wget \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.02-1-src.tar.bz2' \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.02-1.tar.bz2' Uploaded. Anything to remove? 0.98.39-1 maybe? Sure. rm -f nasm-0.98.39-1-src.tar.bz2 nasm-0.98.39-1.tar.bz2 \ nasm-2.00-2-src.tar.bz2 nasm-2.00-2.tar.bz2 will take care of the old packages on the mirrors. -- Dean
Please upload: nasm-2.02-1
Upstream release. wget \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.02-1-src.tar.bz2' \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.02-1.tar.bz2' Thanks. -- Dean
Please upload: nasm-2.01-1
Upstream release. wget \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.01-1-src.tar.bz2' \ 'http://scarff.id.au/file/cygwin/nasm/nasm-2.01-1.tar.bz2' Thanks. -- Dean
please upload: nasm-2.00-2
Fixes a minor packaging bug in 2.00-1. prev set in setup.hint because of a backwards incompatability introduced in 2.00-1. http://scarff.id.au/file/cygwin/nasm/nasm-2.00-2-src.tar.bz2 http://scarff.id.au/file/cygwin/nasm/nasm-2.00-2.tar.bz2 http://scarff.id.au/file/cygwin/nasm/setup.hint Thanks. -- Dean
please upload: nasm-2.00-1
Thanks. http://scarff.id.au/file/cygwin/nasm/nasm-2.00-1-src.tar.bz2 http://scarff.id.au/file/cygwin/nasm/nasm-2.00-1.tar.bz2 http://scarff.id.au/file/cygwin/nasm/setup.hint -- Dean
Re: 3rd summary (was Re: [HEADSUP] ALL Maintainers, please reply.)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Corinna Vinschen writes: Below are the results as of today 2005-10-03. It would be helpful if all maintainers could scan this lists again, so that we're sure that nothing [snip] LIST 3: PACKAGES WITHOUT REPLY FROM MAINTAINER SO FAR = [snip] nasm I maintain nasm, and this is the only package I maintain. - -- Dean -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDQ7BuPs40JFRfzR0RAiWvAJ4tcjxq2HEbNK9xav/AAzyM2gf8FACfbn8d zYcnoY4O/GePjXlMnAp06gI= =zAS5 -END PGP SIGNATURE-
please upload: nasm-0.98.39-1
http://scarff.id.au/file/nasm/nasm-0.98.39-1-src.tar.bz2 http://scarff.id.au/file/nasm/nasm-0.98.39-1.tar.bz2 http://scarff.id.au/file/nasm/setup.hint Upstream ChangeLog: 0.98.39 --- * fix buffer overflow * fix outas86's .bss handling * make spotless no longer deletes config.h.in. * %(el)if(n)idn insensitivity to string quotes difference (#809300). * (nasm.c) __OUTPUT_FORMAT__ changed to string value instead of symbol. sdesc: The Netwide Assembler ldesc: nasm is the famous, portable Netwide Assembler for the 80x86. Many many developers all over the net respect NASM for what it is - a widespread (thus netwide), portable (thus netwide!), very flexible and mature assembler tool with support for many output formats (thus netwide!!). curr: 0.98.39-1 requires: cygwin category: Devel I haven't kept up with the list, so if I've missed any new packaging conventions introduced in the last 8 months, let me know. -- Dean
Re: [ITP] TeXmacs: A scientific wysiwyg Editor and Interface for Computer Algebra Systems
Andreas Seidl wrote: Someone wanted more X-applications? I would like to contribute and maintain TeXmacs: - setup.hint - sdesc: A scientific wysiwyg Editor and Interface for Computer Algebra Systems. ldesc: GNU TeXmacs is a free scientific text editor, which was both inspired by TeX and GNU Emacs. The editor allows you to write structured documents via a wysiwyg (what-you-see-is-what-you-get) and user friendly interface. New styles may be created by the user. The program implements high-quality typesetting algorithms and TeX fonts, which help you to produce professionally looking documents. I vote pro. -- Dean
Re: Pending Packages List, 2003-12-19
Daniel Reed wrote: This is the list of pending packages as of Friday, December 19, 2003. Package: gtypist 2.7-1 [2003-12-09] Description: GNU Typist Proposer: Yaakov Selkowitz Proposal: http://cygwin.com/ml/cygwin-apps/2003-12/msg00127.html Release directory (for use with setup.exe): http://mysite.verizon.net/yselkowitz/cygwin/ http://mysite.verizon.net/yselkowitz/cygwin/release/gtypist/gtypist-2.7-1.tar.bz2 http://mysite.verizon.net/yselkowitz/cygwin/release/gtypist/gtypist-2.7-1-src.tar.bz2 http://mysite.verizon.net/yselkowitz/cygwin/release/gtypist/setup.hint Aye votes: Igor Pechtchanski [1/3] Status: Package available. HOLD-UPS: Not enough votes (need 2 more). No good to go review. +1 vote. The binary package looks good, if it gets the other vote I'll give the source package a review after xmas. Putting it in the games category might also be a good idea. -- Dean
Re: Updated xerces-c 2.4.0-1
Daniel Reed wrote: On 2003-12-17T09:18-0800, Abe Backus wrote: ) The files uploaded appear to have the version 2.4.0-4 in them, when it ) should be 2.4.0-1 That's my mistake; I fixed the XSL, so it shouldn't happen again, but I am not sure whether to rename 2.4.0-4 to 2.4.0-1 or just leave it. For setup-gurus: Would renaming it cause everyone to re-download the package as an update? From setup.html, it would appear so, as long as 2.4.0-1 is marked curr. -- Dean
Re: [RFC] Globally creating a user and a group root
Corinna Vinschen wrote: The remaining problem is the special handling of root. I guess it's best to create the /etc/group entry already in mkgroup. For mkpasswd it might be best, to add a special handling like this: If a Windows user root exists, give it the uid 0. any chance you can poke the base-passwd script soon, to check for a user and a group with SID S-1-1-0 in the existing /etc/passwd and /etc/group files and remove them silently? Also it would be good if the script adds the following entry to /etc/group, if possible as the first line: root:S-1-5-32-544:0: I currently have an entry in /etc/passwd: root:unused_by_nt/2000/xp:500:513:U-SCARFF-BOX\root,S-1-5-21-1606980848-1563985344-1060284298-500:/home/root:/bin/bash This is a side-effect of using mkpasswd with the Administrator user renamed to root on XP. For me (and others like me who renamed the Administrator user) will this cause problems? Forgive me if I've overlooked where this point was addressed before in the thread, I only followed it loosely. -- Dean
nasm 0.98.38-1
New upstream release. Added Charles Bilyue's coff patch (or should I say hack - but it saved me the trouble!), and updated docs to reflect this. Data now in /usr/share like it should be. Source package now has better management for building the extra docs. Built with cygwin 1.5.4-1. sdesc: The Netwide Assembler ldesc: nasm is the famous, portable Netwide Assembler for the 80x86. Many many developers all over the net respect NASM for what it is - a widespread (thus netwide), portable (thus netwide!), very flexible and mature assembler tool with support for many output formats (thus netwide!!). prev: 0.98.36-1 curr: 0.98.38-1 requires: cygwin category: Devel http://www.polarhome.com:753/~p00ya/up/nasm-0.98.38-1-src.tar.bz2 http://www.polarhome.com:753/~p00ya/up/nasm-0.98.38-1.tar.bz2 http://www.polarhome.com:753/~p00ya/up/setup.hint Please upload. Cheers, Dean Scarff sdesc: The Netwide Assembler ldesc: nasm is the famous, portable Netwide Assembler for the 80x86. Many many developers all over the net respect NASM for what it is - a widespread (thus netwide), portable (thus netwide!), very flexible and mature assembler tool with support for many output formats (thus netwide!!). prev: 0.98.36-1 curr: 0.98.38-1 requires: cygwin category: Devel
Re: Packages for upload: nasm (1.3.22 and 1.5.2)
On Sat, 30 Aug 2003 20:26:54 +0200, Gerrit P. Haase wrote: Uploaded; removed 0.98.35-1. Please send an announcement in a couple of hours. Let me know if you want me to remove 0.98.36-1, too. Why not make it prev: for a while, it works well for me and one never knows if the current: has bugs...? Gerrit I'd have no objections here. Although the diff between .36 and .37 isn't very big, it's a good idea. Cheers, Dean Scarff
Packages for upload: nasm (1.3.22 and 1.5.2)
New packages have been built against both cygwin 1.3.22 and 1.5.2 (latest non-snapshot available 30 Aug 2003), for the upstream release of nasm 0.98.37. The 1.5.2-built package is flagged as test; quick tests suggest it's compatible. Other changes: the postscript version of the documentation is no longer used, seeming as it's the same as the info and html outputs, and it just adds to the package size. However, the source package retains all the functionality to build the .ps (and the .pdf if you have gs). sdesc: The Netwide Assembler ldesc: nasm is the famous, portable Netwide Assembler for the 80x86. Many many developers all over the net respect NASM for what it is - a widespread (thus netwide), portable (thus netwide!), very flexible and mature assembler tool with support for many output formats (thus netwide!!). curr: 0.98.37-1 test: 0.98.37-2 # test version is built against cygwin 1.5.2-1 requires: cygwin category: Devel http://www.polarhome.com:753/~p00ya/up/nasm-0.98.37-1.tar.bz2 http://www.polarhome.com:753/~p00ya/up/nasm-0.98.37-1-src.tar.bz2 http://www.polarhome.com:753/~p00ya/up/nasm-0.98.37-2.tar.bz2 http://www.polarhome.com:753/~p00ya/up/nasm-0.98.37-2-src.tar.bz2 http://www.polarhome.com:753/~p00ya/up/setup.hint Please upload Cheers, Dean Scarff
nasm-0.98.36-1
This is the new version of nasm, released on sf March 13. The pdf issue from the 0.98.35 port is still current: again the pdf has been ommitted. setup.hint: http://www.polarhome.com:753/~p00ya/up/setup.hint src package: http://www.polarhome.com:753/~p00ya/up/nasm-0.98.36-1-src.tar.bz2 bin package: http://www.polarhome.com:753/~p00ya/up/nasm-0.98.36-1.tar.bz2 Please upload. Cheers, Dean Scarff -- ___ http://www.operamail.com Now with OperaMail Premium for only US$29.99/yr Powered by Outblaze
Re: [nasm packaging review] was Re: Pending packages status
- Original Message - From: Pavel Tsekov [EMAIL PROTECTED] Date: Mon, 30 Dec 2002 11:11:59 +0100 (CET) On Mon, 30 Dec 2002, Dean Scarff wrote: Done, the new binary package nasm-0.98.35-2 has everything except the pdf (due to ghostscript problems as I mentioned elsewhere). Updated files are here: http://proud-x.com/~p00ya/cygwin-apps/nasm/setup.hint http://proud-x.com/~p00ya/cygwin-apps/nasm/nasm-0.98.35-2.tar.bz2 http://proud-x.com/~p00ya/cygwin-apps/nasm/nasm-0.98.35-2-src.tar.bz2 Ok, I've just reviewed the package. Do you mind moving the contents of /usr/doc/nasm to /usr/doc/nasm-0.98.35 ? Btw, please, do not update the cygwin specific part of the package version number when releasing an updated version in the process of reviewing. My mistake, both the above points are fixed now. The new binary package looks like: usr/ usr/man/ usr/man/man1/ usr/man/man1/nasm.1 usr/man/man1/ndisasm.1 usr/info/ usr/info/nasm.info usr/info/nasm.info-1 usr/info/nasm.info-10 usr/info/nasm.info-11 usr/info/nasm.info-12 usr/info/nasm.info-13 usr/info/nasm.info-14 usr/info/nasm.info-2 usr/info/nasm.info-3 usr/info/nasm.info-4 usr/info/nasm.info-5 usr/info/nasm.info-6 usr/info/nasm.info-7 usr/info/nasm.info-8 usr/info/nasm.info-9 usr/bin/ usr/bin/rdf2com.exe usr/bin/nasm.exe usr/bin/ndisasm.exe usr/bin/rdfdump.exe usr/bin/ldrdf.exe usr/bin/rdx.exe usr/bin/rdflib.exe usr/bin/rdf2bin.exe usr/bin/rdf2ihx.exe usr/doc/ usr/doc/nasm-0.98.35/ usr/doc/nasm-0.98.35/html/ usr/doc/nasm-0.98.35/html/nasmdo10.html usr/doc/nasm-0.98.35/html/nasmdoc0.html usr/doc/nasm-0.98.35/html/nasmdoc1.html usr/doc/nasm-0.98.35/html/nasmdoc2.html usr/doc/nasm-0.98.35/html/nasmdoc3.html usr/doc/nasm-0.98.35/html/nasmdoc4.html usr/doc/nasm-0.98.35/html/nasmdoc5.html usr/doc/nasm-0.98.35/html/nasmdoc6.html usr/doc/nasm-0.98.35/html/nasmdoc7.html usr/doc/nasm-0.98.35/html/nasmdoc8.html usr/doc/nasm-0.98.35/html/nasmdoc9.html usr/doc/nasm-0.98.35/html/nasmdoca.html usr/doc/nasm-0.98.35/html/nasmdocb.html usr/doc/nasm-0.98.35/html/nasmdoci.html usr/doc/nasm-0.98.35/nasmdoc.ps usr/doc/nasm-0.98.35/nasmdoc.txt usr/doc/nasm-0.98.35/AUTHORS usr/doc/nasm-0.98.35/CHANGES usr/doc/nasm-0.98.35/INSTALL usr/doc/nasm-0.98.35/COPYING usr/doc/nasm-0.98.35/README usr/doc/nasm-0.98.35/TODO usr/doc/nasm-0.98.35/ChangeLog usr/doc/Cygwin/ usr/doc/Cygwin/nasm-0.98.35.README Updated files are at: http://proud-x.com/~p00ya/cygwin-apps/nasm/setup.hint http://proud-x.com/~p00ya/cygwin-apps/nasm/nasm-0.98.35-1.tar.bz2 http://proud-x.com/~p00ya/cygwin-apps/nasm/nasm-0.98.35-1-src.tar.bz2 Cheers, Dean Scarff -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze
Re: [nasm packaging review] was Re: Pending packages status
From: Dario Alcocer alcocer at helixdigital dot com Date: Mon, 30 Dec 2002 18:35:28 -0800 What problems exactly are you having with Ghostscript? I'll assume that you're referring to the Cygwin version of Ghostscript. They may not be a problem with ghostscript at all, contrary to what I said before. It may actually be a problem with the .ps that was generated. I have no experience with either format, but here's the error message from ps2pdf: $ ps2pdf -dOptimize=true nasmdoc.ps nasmdoc.pdf Error: /undefined in setpagesize Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval- - 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- fa lse 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop .runexec 2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push -- nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1085/1123(ro)(G)-- --dict:0/20(G)-- --dict:111/200(L)-- Current allocation mode is local Current file position is 52386 GNU Ghostscript 7.05: Unrecoverable error, exit code 1 The .ps was generated from a perl script that exited without error. The build works on debian with perl 5.8.0 and GNU Ghostscript 7.05. I'm using those same versions of each on cywin. I'm sorry for assuming this was a problem with ghostscript if it isn't. If you or anyone knows the source of this problem, I'd be happy to know. Otherwise, I'm quite happy to leave the pdf out - it would double the size of the binary package, and its not a format that is particularly useful (imho) in cygwin when there's html as well. Cheers, Dean Scarff -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze
Re: [nasm packaging review] was Re: Pending packages status
- Original Message - From: Pavel Tsekov [EMAIL PROTECTED] Date: Thu, 26 Dec 2002 18:37:20 +0100 (CET) To: [EMAIL PROTECTED] Subject: [nasm packaging review] was Re: Pending packages status On Tue, 24 Dec 2002, Pavel Tsekov wrote: 4. nasm version: 0.98.35-1 status : not reviewed I've reviewed the packaging of nasm and it seems to be OK. The only thing that seems to be missing is the documentation. The documentation provided by the binary package includes only the man pages for nasm and ndisasm. However, nasm has a very complete documentation with a lot of examples and available in several differen output formats (html, info, pdf). So, I think including one the .info files in the binary package along with the man pages is a good idea and will make the package complete. Done, the new binary package nasm-0.98.35-2 has everything except the pdf (due to ghostscript problems as I mentioned elsewhere). Updated files are here: http://proud-x.com/~p00ya/cygwin-apps/nasm/setup.hint http://proud-x.com/~p00ya/cygwin-apps/nasm/nasm-0.98.35-2.tar.bz2 http://proud-x.com/~p00ya/cygwin-apps/nasm/nasm-0.98.35-2-src.tar.bz2 Cheers, Dean Scarff -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze
Re: [nasm packaging review] was Re: Pending packages status
- Original Message - From: Joshua Daniel Franklin [EMAIL PROTECTED] Date: Thu, 26 Dec 2002 11:02:09 -0800 (PST) To: [EMAIL PROTECTED] Subject: Re: [nasm packaging review] was Re: Pending packages status ... An alternative would be to have a separate nasm-doc package with all the documentation, which would keep the smaller binary download for people that do not need the docs. I agree that both the man and info docs should be available in the binary distribution. As for the additional (pdf, ps, html) documentation, I'm open to suggestion. The extra docs are certainly very comprehensive, although I don't often consult them. I also notice that the nasm project provides a separate nasm-0.98.35-xdoc package. In any case, I'll repackage the existing package to make everything and make install_everything, I'll post an update soon. Cheers, Dean Scarff -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze
[adding docs to nasm] unfulfilled build deps for pdf
As per your suggestion to add the extra docs to the nasm package, I have found that nasm requires AFPL ghostscript to build the pdf. This package is not currently part of cygwin (although there is an old contrib that never made it here: http://sources.redhat.com/ml/cygwin-apps/2002-10/msg00185.html ). So my question is, is there a policy regarding relying on non-(official)cygwin packages for builds? I can easily just add the pdf built on linux to the binary package, but this would mean that the source package will be incapable (under cygwin) of producing the binary. The other option as Joshua suggested is to provide a separate docs package (which doesnt need a corresponding source). Cheers, Dean Scarff -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze
