This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: for generic-build-script
Yaakov schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Gerrit P. Haase wrote:
|>>>and not pages that were already compressed (I've built a couple
|>>of programs that would gzip the man pages themselves on install).
> |
> | gzip takes care of it.
> More correctly, gzip -q won't complain about it. But without the -q
> flag, you get:
> $ gzip test.tar.gz
> gzip: test.tar.gz already has .gz suffix -- unchanged
> So I think it's not optimal to be (trying) to gzip *.gz files, even if
> the -q flag keeps gzip from complaining.
And -f overwrites the existing .gz files if there are any.
|>>But I see now with the info pages that it's more complicated than *.info
|>>in the cases when there are multiple info page files for one program,
|>>such as gcc, gdb, make, emacs, etc. Is that what your intention is?
> |
> | Exact. The "*.info" does not match on "*.info-1".
> That's what I thought, but you didn't explain yourself before.
> | Yes, looks better (not tested yet), but why not go the easy way? Look
> | what I do for GCC:
> |
> | ( cd ${PKG1}${prefix}/share/info ; rm -f dir ; gzip -fq9 * ) && \
> | ( cd ${PKG1}${prefix}/share/man && gzip -fq9 */* ) && \
> This may work for gcc, but remember this is a *generic* build-script.
> Some packages contain foreign-language man pages, which are stored as
> /usr/share/man/de/man1, for example, and the above would not work in
> such a case.
Point for you!
> There are a few such package in the distro already (I noticed dpkg,
> man, and WindowMaker), and I have built other such packages myself.
> Hence, I think using find is the only way to correctly do this.
Alright, I agree.
Gerrit
--
=^..^=