[gentoo-dev] Gzipped HTML docs in /usr/share/doc

[gentoo-dev] Gzipped HTML docs in /usr/share/doc

[Stefan Boresch]

I have recently stumbled across a lot of gzipped *.html *.htm
files in the /usr/share/doc hierarchy.  I don't like it very much
since this breaks all navigation links.  My question is: is this
intended, should I write bug reports, should I submit patches (provided
I figure out who is the 'culprit' for the compression (I suppose this is
a 'feature' of ebuild at some level)

Thanks,

Stefan Boresch

PS: Assuming that the compression of documentation is done
semi-automatically by ebuild, might it not be the easiest to either
exclude htm(l) pages from compression, or make the behavior user
controllable...?

AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc

[Sebastian Werner]

You are right. Leave all directories which contains html-documentation
without compression or put all files in one tar file and compress this
file.

Greetings

Sebastian

-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@gentoo.org [mailto:gentoo-dev-admin@gentoo.org] Im
Auftrag von Stefan Boresch
Gesendet: Dienstag, 19. Februar 2002 09:04
An: gentoo-dev@gentoo.org
Betreff: [gentoo-dev] Gzipped HTML docs in /usr/share/doc

I have recently stumbled across a lot of gzipped *.html *.htm
files in the /usr/share/doc hierarchy.  I don't like it very much
since this breaks all navigation links.  My question is: is this
intended, should I write bug reports, should I submit patches (provided
I figure out who is the 'culprit' for the compression (I suppose this is
a 'feature' of ebuild at some level)

Thanks,

Stefan Boresch

PS: Assuming that the compression of documentation is done
semi-automatically by ebuild, might it not be the easiest to either
exclude htm(l) pages from compression, or make the behavior user
controllable...?




_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] Gzipped HTML docs in /usr/share/doc

[Chris Houser]

There is a "dohtml" command available in ebuild scripts for just this
purpose.  I think you should feel free to file bugs against any ebuild
that installs html files in compressed form.

--Chouser

Sebastian Werner wrote:               [Tue Feb 19 2002,  3:57:03AM EST]         
> You are right. Leave all directories which contains html-documentation
> without compression or put all files in one tar file and compress this
> file.
> 
> Greetings
> 
> Sebastian
> 
> -----Ursprüngliche Nachricht-----
> Von: gentoo-dev-admin@gentoo.org [mailto:gentoo-dev-admin@gentoo.org] Im
> Auftrag von Stefan Boresch
> Gesendet: Dienstag, 19. Februar 2002 09:04
> An: gentoo-dev@gentoo.org
> Betreff: [gentoo-dev] Gzipped HTML docs in /usr/share/doc
> 
> I have recently stumbled across a lot of gzipped *.html *.htm
> files in the /usr/share/doc hierarchy.  I don't like it very much
> since this breaks all navigation links.  My question is: is this
> intended, should I write bug reports, should I submit patches (provided
> I figure out who is the 'culprit' for the compression (I suppose this is
> a 'feature' of ebuild at some level)
> 
> Thanks,
> 
> Stefan Boresch
> 
> PS: Assuming that the compression of documentation is done
> semi-automatically by ebuild, might it not be the easiest to either
> exclude htm(l) pages from compression, or make the behavior user
> controllable...?
> 
> 
> 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

Re: AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc

[Stefan Boresch]

Thanks for the answer!

On Tue, 2002-02-19 at 09:57, Sebastian Werner wrote:
> You are right. Leave all directories which contains html-documentation
> without compression or put all files in one tar file and compress this
> file.

Nevertheless, what am I supposed to do? Write (a) bug report(s) (submit
patches) for each package with gzipped HTML docs I run across --- there
seem to be a lot... Or, and this makes this a more general question,
can/could this be handled on the portage/ebuild level? (I am still
at portage 1.8.8)

I guess I'am expecting (hoping for) some response from
management. Let me know whether to shut up, swamp bugs.gentoo.org
or to look into modifying ebuild (the latter may turn out problematic,
as my programming experience is rather limited...)   

Cheers,

Stefan

Re: AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc

[Arcady Genkin]

Stefan Boresch <stefan@mdy.univie.ac.at> writes:

> I guess I'am expecting (hoping for) some response from
> management. Let me know whether to shut up, swamp bugs.gentoo.org
> or to look into modifying ebuild (the latter may turn out problematic,
> as my programming experience is rather limited...)   

I am not the ``management'', but IMO if you could gather the names of
the packages which don't do the right thing with the HTML
documentation into a list, and submit it as one bug, it would,
probably, do.  The coding solution to this problem is rather trivial.
Submitting one bug report per package would also be fine, I guess, but
it would take a lot of your time if there are more than a few.
-- 
Arcady Genkin
Don't read everyting you believe.