[pacman-dev] handling info files
Now that we decided that we want to ship info documentation we should decide how to package such files: info files could be gzipped by makepkg or stay uncompressed. On my system they already take quiet a lot of space compared to much more packages shipping man-pages: [root@workstation64 andyrtr]# du -ch /usr/share/info/ 21M /usr/share/info/ [root@workstation64 andyrtr]# du -sch /usr/share/man 61M /usr/share/man Some are really big like gcc.info being 1.8mb uncompressed. I vote for auto-gzipping the info pages like man-pages. And shouldn't we check and remove the $pkgdir/usr/share/info/dir file that every pkg with info files produces? Maybe we can also print at the end of the makepkg run an array of found info files the packager should put into the *.install file. Right now we use the proto-info.install shipped with the "abs" pkg. An automated solution would be also nice for that. Opinions? -Andy
On Wed, Sep 17, 2008 at 12:23 PM, Andreas Radke <a.radke@arcor.de> wrote:
Now that we decided that we want to ship info documentation we should decide how to package such files: info files could be gzipped by makepkg or stay uncompressed.
On my system they already take quiet a lot of space compared to much more packages shipping man-pages:
[root@workstation64 andyrtr]# du -ch /usr/share/info/ 21M /usr/share/info/ [root@workstation64 andyrtr]# du -sch /usr/share/man 61M /usr/share/man
Some are really big like gcc.info being 1.8mb uncompressed. I vote for auto-gzipping the info pages like man-pages.
And shouldn't we check and remove the $pkgdir/usr/share/info/dir file that every pkg with info files produces?
Maybe we can also print at the end of the makepkg run an array of found info files the packager should put into the *.install file. Right now we use the proto-info.install shipped with the "abs" pkg. An automated solution would be also nice for that.
Opinions?
Hmm, I've been thinking about this too, but I was hoping to avoid special-case code for some of this. But maybe we should, at least, automate the removal of the dir file... With regard to printing info files, that seems easy enough with something like "tar tzf <pkgfile> | grep info"
2008/9/17 Andreas Radke <a.radke@arcor.de>:
Now that we decided that we want to ship info documentation we should decide how to package such files: info files could be gzipped by makepkg or stay uncompressed.
On my system they already take quiet a lot of space compared to much more packages shipping man-pages:
[root@workstation64 andyrtr]# du -ch /usr/share/info/ 21M /usr/share/info/ [root@workstation64 andyrtr]# du -sch /usr/share/man 61M /usr/share/man
Some are really big like gcc.info being 1.8mb uncompressed. I vote for auto-gzipping the info pages like man-pages.
And shouldn't we check and remove the $pkgdir/usr/share/info/dir file that every pkg with info files produces?
I thought that 'zipman' in makepkg.conf do this for info pages too. -- Roman Kyrylych (Роман Кирилич)
Roman Kyrylych wrote:
2008/9/17 Andreas Radke <a.radke@arcor.de>:
Now that we decided that we want to ship info documentation we should decide how to package such files: info files could be gzipped by makepkg or stay uncompressed.
On my system they already take quiet a lot of space compared to much more packages shipping man-pages:
[root@workstation64 andyrtr]# du -ch /usr/share/info/ 21M /usr/share/info/ [root@workstation64 andyrtr]# du -sch /usr/share/man 61M /usr/share/man
Some are really big like gcc.info being 1.8mb uncompressed. I vote for auto-gzipping the info pages like man-pages.
And shouldn't we check and remove the $pkgdir/usr/share/info/dir file that every pkg with info files produces?
I thought that 'zipman' in makepkg.conf do this for info pages too.
Yes, but the compressing of info pages is only on the master branch. There is no automatic removing of the dir file but that would require hard-coding a file name into makepkg which I am not too sure about...
participants (4)
-
Aaron Griffin
-
Allan McRae
-
Andreas Radke
-
Roman Kyrylych