FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 08-02-2008, 02:12 AM
Allan McRae
 
Default info pages

Hi all,

Just a heads up with something I have remembered while packaging with
the new pacman release. Including docs is the default in makepkg.conf
now so if there is a large amount of documentation you will want to add
a !docs to the PKGBUILD options. Also, every package that needs the
--mandir configure flag will probably need and --infodir one too. An
annoying number of packages with info pages install a
/usr/share/info/dir file so that will need removed at the end of the
PKGBUILD.


Cheers,
Allan
 
Old 08-05-2008, 11:53 PM
Allan McRae
 
Default info pages

Allan McRae wrote:

Hi all,

Just a heads up with something I have remembered while packaging with
the new pacman release. Including docs is the default in makepkg.conf
now so if there is a large amount of documentation you will want to
add a !docs to the PKGBUILD options. Also, every package that needs
the --mandir configure flag will probably need and --infodir one too.
An annoying number of packages with info pages install a
/usr/share/info/dir file so that will need removed at the end of the
PKGBUILD.




I have discovered that at least one package has to have a
/usr/share/info/dir file or the info command complains that it is
missing. It seems that ideally all packages with info directories
should add/remove entries in this file when installing/removing the
package, although calling "info <something not in dir file>" seems to
work, but I might be missing something....

The point is that adding info files properly involves an install file
with "install-info" commands for each info page in the package. Isn't
including docs fun!


Allan
 
Old 08-08-2008, 11:43 PM
Eric Belanger
 
Default info pages

On Wed, 6 Aug 2008, Allan McRae wrote:


Allan McRae wrote:

Hi all,

Just a heads up with something I have remembered while packaging with the
new pacman release. Including docs is the default in makepkg.conf now so
if there is a large amount of documentation you will want to add a !docs to
the PKGBUILD options. Also, every package that needs the --mandir
configure flag will probably need and --infodir one too. An annoying
number of packages with info pages install a /usr/share/info/dir file so
that will need removed at the end of the PKGBUILD.




I have discovered that at least one package has to have a /usr/share/info/dir
file or the info command complains that it is missing. It seems that
ideally all packages with info directories should add/remove entries in this
file when installing/removing the package, although calling "info <something
not in dir file>" seems to work, but I might be missing something....
The point is that adding info files properly involves an install file with
"install-info" commands for each info page in the package. Isn't including
docs fun!


Allan



The emacs package already does this. The emacs.install file could be used
as a template for this info stuff.


Eric

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
 
Old 08-09-2008, 02:12 AM
Allan McRae
 
Default info pages

Eric Belanger wrote:

On Wed, 6 Aug 2008, Allan McRae wrote:


Allan McRae wrote:

Hi all,

Just a heads up with something I have remembered while packaging
with the new pacman release. Including docs is the default in
makepkg.conf now so if there is a large amount of documentation you
will want to add a !docs to the PKGBUILD options. Also, every
package that needs the --mandir configure flag will probably need
and --infodir one too. An annoying number of packages with info
pages install a /usr/share/info/dir file so that will need removed
at the end of the PKGBUILD.




I have discovered that at least one package has to have a
/usr/share/info/dir file or the info command complains that it is
missing. It seems that ideally all packages with info directories
should add/remove entries in this file when installing/removing the
package, although calling "info <something not in dir file>" seems to
work, but I might be missing something.... The point is that adding
info files properly involves an install file with "install-info"
commands for each info page in the package. Isn't including docs fun!


Allan



The emacs package already does this. The emacs.install file could be
used as a template for this info stuff.




A template based in that is making its way into the prototypes found in
the ABS packages which I am going to make a release of soon.


CC: pacman-dev - We should also automatically compress the info files
like we do the man pages.


Allan
 
Old 08-09-2008, 02:12 AM
Allan McRae
 
Default info pages

Eric Belanger wrote:

On Wed, 6 Aug 2008, Allan McRae wrote:


Allan McRae wrote:

Hi all,

Just a heads up with something I have remembered while packaging
with the new pacman release. Including docs is the default in
makepkg.conf now so if there is a large amount of documentation you
will want to add a !docs to the PKGBUILD options. Also, every
package that needs the --mandir configure flag will probably need
and --infodir one too. An annoying number of packages with info
pages install a /usr/share/info/dir file so that will need removed
at the end of the PKGBUILD.




I have discovered that at least one package has to have a
/usr/share/info/dir file or the info command complains that it is
missing. It seems that ideally all packages with info directories
should add/remove entries in this file when installing/removing the
package, although calling "info <something not in dir file>" seems to
work, but I might be missing something.... The point is that adding
info files properly involves an install file with "install-info"
commands for each info page in the package. Isn't including docs fun!


Allan



The emacs package already does this. The emacs.install file could be
used as a template for this info stuff.




A template based in that is making its way into the prototypes found in
the ABS packages which I am going to make a release of soon.


CC: pacman-dev - We should also automatically compress the info files
like we do the man pages.


Allan



_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 08-09-2008, 02:48 AM
Allan McRae
 
Default info pages

Allan McRae wrote:
We should also automatically compress the info files like we do the
man pages.


Would there be any objects to extending the zipman option to cover the
compressing of info pages too?

Also, I can see two options for doing this. 1) Just add the info
directories to the "mandirs" array. 2) Compress info pages separately
as I think the whole hardlink checking is not needed for info pages. I
am leaning towards #1.


Allan


_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 08-09-2008, 02:58 PM
"Dan McGee"
 
Default info pages

On Fri, Aug 8, 2008 at 9:48 PM, Allan McRae <allan@archlinux.org> wrote:
> Allan McRae wrote:
>>
>> We should also automatically compress the info files like we do the man
>> pages.
>
> Would there be any objects to extending the zipman option to cover the
> compressing of info pages too?
> Also, I can see two options for doing this. 1) Just add the info
> directories to the "mandirs" array. 2) Compress info pages separately as I
> think the whole hardlink checking is not needed for info pages. I am
> leaning towards #1.

I think 1 is fine.

Hindsight would have named these things 'zipdoc' and 'docdirs', damn.

-Dan
_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 08-09-2008, 04:00 PM
Miklos Vajna
 
Default info pages

On Sat, Aug 09, 2008 at 12:12:29PM +1000, Allan McRae <allan@archlinux.org> wrote:
> CC: pacman-dev - We should also automatically compress the info files like
> we do the man pages.

That should not be hard, we have this trivial commit since a while:

http://git.frugalware.org/gitweb/gitweb.cgi?p=pacman-g2.git;a=commitdiff;h=e804504286ecdb6eee56a26bfaf7 431728ff2507
_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 08-09-2008, 05:43 PM
"Dan McGee"
 
Default info pages

On Sat, Aug 9, 2008 at 11:00 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Sat, Aug 09, 2008 at 12:12:29PM +1000, Allan McRae <allan@archlinux.org> wrote:
>> CC: pacman-dev - We should also automatically compress the info files like
>> we do the man pages.
>
> That should not be hard, we have this trivial commit since a while:
>
> http://git.frugalware.org/gitweb/gitweb.cgi?p=pacman-g2.git;a=commitdiff;h=e804504286ecdb6eee56a26bfaf7 431728ff2507

Do we do something like the following, or do we hardcode the info dirs
as well? It seems odd how we laid this out looking back, where the
DOC_DIRS location is specified but not the mandirs.

diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
index c5dbed9..8feeed3 100644
--- a/scripts/makepkg.sh.in
+++ b/scripts/makepkg.sh.in
@@ -685,9 +685,10 @@ tidy_install() {
fi

if [ "$(check_option zipman)" = "y" ]; then
- msg2 "$(gettext "Compressing man pages...")"
+ msg2 "$(gettext "Compressing documentation...")"
local manpage mandirs ext file link hardlinks hl
mandirs="usr/man usr/share/man usr/local/man
usr/local/share/man opt/*/man"
+ mandirs="$mandirs ${DOC_DIRS}"
find ${mandirs} -type f 2>/dev/null |
while read manpage ; do
# check file still exists (potentially
compressed with hard link)
_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 08-10-2008, 01:33 PM
Allan McRae
 
Default info pages

Dan McGee wrote:

On Sat, Aug 9, 2008 at 11:00 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:


On Sat, Aug 09, 2008 at 12:12:29PM +1000, Allan McRae <allan@archlinux.org> wrote:


CC: pacman-dev - We should also automatically compress the info files like
we do the man pages.


That should not be hard, we have this trivial commit since a while:

http://git.frugalware.org/gitweb/gitweb.cgi?p=pacman-g2.git;a=commitdiff;h=e804504286ecdb6eee56a26bfaf7 431728ff2507



Do we do something like the following, or do we hardcode the info dirs
as well? It seems odd how we laid this out looking back, where the
DOC_DIRS location is specified but not the mandirs.

diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in
index c5dbed9..8feeed3 100644
--- a/scripts/makepkg.sh.in
+++ b/scripts/makepkg.sh.in
@@ -685,9 +685,10 @@ tidy_install() {
fi

if [ "$(check_option zipman)" = "y" ]; then
- msg2 "$(gettext "Compressing man pages...")"
+ msg2 "$(gettext "Compressing documentation...")"
local manpage mandirs ext file link hardlinks hl
mandirs="usr/man usr/share/man usr/local/man
usr/local/share/man opt/*/man"
+ mandirs="$mandirs ${DOC_DIRS}"
find ${mandirs} -type f 2>/dev/null |
while read manpage ; do
# check file still exists (potentially
compressed with hard link)


Won't that compress e.g. html documentation in ${DOC_DIRS} as well? In
general, that would be bad.


I know the reasons are historical, but from a makepkg point of view, why
are man pages treated as different from info pages? I see a good reason
for treating the rest of documentation different. As far as makepkg is
concerned man and info pages both need treated the same. So should info
be removed from the DOC_DIRS variable? Kind of makes the including docs
by default redundant if we do that though...


Allan


_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 

Thread Tools




All times are GMT. The time now is 02:00 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org