On Mon, Oct 05, 2009 at 03:26:43PM +, Marco Atzeri wrote:
Hi Christopher,
when do you plan to bump the cygwin-doc package to align with
the new documentation ?
http://cygwin.com/1.7/cygwin-ug-net/cygwin-ug-net.html
http://cygwin.com/1.7/cygwin-api/cygwin-api.html
On 10/6/05, Igor Pechtchanski wrote:
I just installed xmlto/docbook-xsl, and tried to build the Cygwin
documentation. It seems that it's trying to connect to oasis-open.org,
probably to get some DTD that's included from one of the cygwin-doc
DTDs. Is this supposed to happen? Can there be a
On Dec 30 17:33, Joshua Daniel Franklin wrote:
http://ns1.iocc.com/~joshua/cygwin/cygwin-doc-1.4-1.tar.bz2
http://ns1.iocc.com/~joshua/cygwin/cygwin-doc-1.4-1-src.tar.bz2
http://ns1.iocc.com/~joshua/cygwin/setup.hint
Uploaded.
Corinna
--
Corinna Vinschen Please, send mails
Well, no thanks to you bozos I fixed my own problems. These packages
are ready to upload. They are a *major* upgrade from the other cygwin-doc
package in that they now include the newlib man pages and the HTML FAQ,
User's Guide, and API Reference. I tracked down upset and now
On Thu, Aug 01, 2002 at 09:08:50PM -0500, Joshua Daniel Franklin wrote:
Well, no thanks to you bozos I fixed my own problems. These packages
are ready to upload. They are a *major* upgrade from the other cygwin-doc
package in that they now include the newlib man pages and the HTML FAQ,
User's
How would you feel about including the libc*.info and libm.info files in
cygwin-doc?
Well, not so good after I realized that I can't build them on my machine.
I read your newlib mailing list post and thought, Hey, that's weird, I
don't remember seeing errors building newlib/doc... and then
On Thu, Aug 01, 2002 at 09:25:41PM -0500, Joshua Daniel Franklin wrote:
How would you feel about including the libc*.info and libm.info files
in cygwin-doc?
Well, not so good after I realized that I can't build them on my
machine. I read your newlib mailing list post and thought, Hey,
that's
How would you feel about including the libc*.info and libm.info files
in cygwin-doc?
Well, not so good after I realized that I can't build them on my
machine. I read your newlib mailing list post and thought, Hey,
that's weird, I don't remember seeing errors building newlib/doc...
and
On Thu, Aug 01, 2002 at 09:59:01PM -0500, Joshua Daniel Franklin wrote:
How would you feel about including the libc*.info and libm.info files
in cygwin-doc?
Well, not so good after I realized that I can't build them on my
machine. I read your newlib mailing list post and thought, Hey,
I'll do those. What about coordinating with the cygwin package to
prevent overlap?
Hmm. Good point. I guess I should release a 1.3.12-3 without those
packages.
I'll do that right now.
OK, I've got the packages with /usr/info/lib* and install-info in
the postinstall script. I also put
Joshua,
I meant to ask if you would mind mentioning the fact that the new
1.3.12-3 cygwin release has only deleted the info files in favor of
cygwin-doc when you send your message to cygwin-announce. I don't think
it is worth sending another cygwin release announcement just for this since
there
On Tue, Apr 16, 2002 at 07:00:03PM -0700, Joshua Daniel Franklin wrote:
In-Reply-To: [EMAIL PROTECTED]
But, where would the user find the info file? It isn't in any distribution
yet.
OK, the bad news is
1. newlib doesn't have any real texinfo documentation.
There's headers, for example
In-Reply-To: [EMAIL PROTECTED]
I wanted to have one place where people could get the cygwin docs.
I want this too. It's just that the pieces aren't in place for it yet.
However, given the above observations, I think it makes sense to forget
about this for now. So, I have no objections to
I just checked the discussion about this, and you asked if someone was
already maintaining newlib-man. I don't think I ever answered but the
answer is no. It looks like the man pages aren't even generated by
newlib anymore. Instead there is a big info file generated by 'make info'.
Any
On Mon, Apr 15, 2002 at 08:00:08PM -0700, Joshua Daniel Franklin wrote:
I just checked the discussion about this, and you asked if someone was
already maintaining newlib-man. I don't think I ever answered but the
answer is no. It looks like the man pages aren't even generated by
newlib anymore.
AFAIK, setup doesn't handle buildRequires. What I've been doing is to
only list runtime dependencies for the binary package in the Requires:
line, and then just mention the buildtime requirements in the readme.
e.g. you don't list gcc/binutils in the Requires: line of every package.
--Chuck
From cinstall/README:
WISHLIST:
...
* build-depends
Rob
--- Robert Collins [EMAIL PROTECTED] wrote:
From cinstall/README:
WISHLIST:
...
* build-depends
Rob
Scratch that, Chuck is right--sometimes I might want to just look at
how something was done, but if I don't have gcc, binutils, make, ...
installed I don't want setup grabbing them!
From: Joshua Daniel Franklin [EMAIL PROTECTED]
To: Michael A Chase [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, April 13, 2002 09:48
Subject: Re: cygwin-doc
Thanks, I fixed this. (Well, I fixed intro.1, which I assume you meant.)
It was.
Man puts a preprocessed copy of /usr/man/man1
-Original Message-
From: Joshua Daniel Franklin [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 14, 2002 2:29 AM
To: Robert Collins; Charles Wilson
Cc: [EMAIL PROTECTED]
Subject: RE: cygwin-doc
--- Robert Collins [EMAIL PROTECTED] wrote:
From cinstall/README
Are you kidding? Cygwin-Man is the COOLEST!
And would make a great mascot!
Truth, Justice, and the American Way, my friend. Truth, Justice, and the
American Way.
Just think of it this way: instead of just some 'man' now we've got a
'doc'. Hmmm... I wonder if people are going to think
http://cygwin.com/cygwin-api/cygwin-api.html;;
^^
Sorry, too much perl.
sdesc: Cygwin-specific man-pages for utilities and functions
ldesc: The intro.1 and intro.3 man pages for Cygwin. Also includes
autogenerated,
I haven't had time to look at all the man pages in detail, but image.1
appears to be bzip2 compressed tarball instead of a man page.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Give a hobbit
The first thing I thought of is that if I added texinfo later, cygwin-man
would be a bad name to have,
Are you kidding? Cygwin-Man is the COOLEST! Remember that one time when he
flew around the world so fast that he made time run backwards? That was
AWESOME! And how he can outrun a train?
24 matches
Mail list logo
