Re: testing release of Perl packages
-----BEGIN PGP SIGNED MESSAGE-----
Raphael Hertzog, in an immanent manifestation of deity, wrote:
>Le Wed, Jun 23, 1999 at 04:20:10AM -0700, Darren/Torin/Who Ever... écrivait:
>> b) The symlinks in /usr/doc for the fake packages are showing up as
>> real directories (see my post on debian-devel)
>
>If I remember well, this is a known bug of dpkg, it doesn't create the
>symlink if something else existed before ...
It's not that big of a deal. I'll fix it in a version or two. I'd
prefer we do safe over correct here.
>> c) Aborting the installation of perl-5.005-base doesn't stop the
>> unpacking of perl-5.005 and friends. (See my post on
>> debian-devel)
Actually, I'm just going to tell them what happened. You can still use
perl-5.004 while 5.005 is installed, so there is no reason to abort the
installation.
>> a) Install the new Perl Policy Paper from Raphael.
>> b) Hopefully this includes registering with doc-base but I don't
>> promise anything
>
>The doc-base registration is not very hard. Even simpler with debhelper.
It was easy. My problem came from debiandoc2html. It insisted on
putting the files in a '.html' directory. That's what mv is for...
Could you vet these changes that I made to your doc? There are no
substance changes. It's mostly capitalizing and a few misspellings.
I am curious about the e in your first name. Is it accent grave or
accent acute?
Darren
--- perl-policy.sgml~1~ Fri Jun 25 03:55:08 1999
+++ perl-policy.sgml Fri Jun 25 02:45:32 1999
@@ -1,11 +1,11 @@
<!doctype debiandoc system>
<book>
<title>Debian Perl policy
-<author><name/Raphaël Hertzog/ <email/hertzog@debian.org/
+<author><name/Raphael Hertzog/ <email/hertzog@debian.org/
<version>1.0
<abstract>
-This document explains how perl stuff is packaged within Debian.
+This document explains how Perl stuff is packaged within Debian.
<copyright>Copyright 1999 by the Debian Project
<p>
@@ -23,19 +23,19 @@
<toc>
-<chapt>General view of perl stuff on a Debian system
+<chapt>General view of Perl stuff on a Debian system
-<p>Debian has decided to enable developers to have more than one perl on
+<p>Debian has decided to enable developers to have more than one Perl on
their system. You can have perl-5.004 and perl-5.005. However only one version
-of perl will be officially blessed at a time. This official version should
-be used to build all perl modules. The current policy is to bless the more
-recent perl available in Debian. The official perl will always be available
-under /usr/bin/perl. Older perls will be available as /usr/bin/perl-$version.
+of Perl will be officially blessed at a time. This official version should
+be used to build all Perl modules. The current policy is to bless the more
+recent Perl available in Debian. The official Perl will always be available
+under /usr/bin/perl. Older Perls will be available as /usr/bin/perl-$version.
-<p>This choice has many consequences on how modules and perl itself are
+<p>This choice has many consequences on how modules and Perl itself are
packaged. You'll find all the details in the following chapters.
-<chapt>How perl itself is packaged
+<chapt>How Perl itself is packaged
<p>Each perl-$version source package will build at least
perl-$version-base, perl-$version, perl-$version-doc,
@@ -47,13 +47,13 @@
maintainer. :-)
<p>As perl-5.004 and perl-5.005 may be installed at the same time,
-the files must be installed in versionned directories so that one package
+the files must be installed in versioned directories so that one package
does not overwrite the other's files. But they should cooperate so that
-the man page refers to the good version of perl (/usr/bin/perl) and so that
-/usr/bin/perl will always be the latest perl.
+the man page refers to the good version of Perl (/usr/bin/perl) and so that
+/usr/bin/perl will always be the latest Perl.
<p>Perl should always look for modules in /usr/lib/perl5 as it's the
- standard directory used for installing non-binary perl modules.
+ standard directory used for installing non-binary Perl modules.
<sect>perl-$version-base
@@ -68,20 +68,20 @@
<sect>perl-$version
-<p>This is the standard perl package containing all the modules
-shipped with the perl sources. It should provide perl5 so that
-perl scripts do not need to worry about which perl-$version is the
+<p>This is the standard Perl package containing all the modules
+shipped with the Perl sources. It should provide perl5 so that
+Perl scripts do not need to worry about which perl-$version is the
current one. It does depend on perl-$version-base as it does not
-provide the perl binary.
+provide the Perl binary.
-<chapt>Packaging perl modules
+<chapt>Packaging Perl modules
<sect>Recommendations for all modules
<p>First, if you package a module Foo::Bar you should call your
package libfoo-bar-perl.
-<p>In order to configure your perl module you can use something like this :
+<p>In order to configure your Perl module you can use something like this :
<p>At the top of debian/rules :
<example>
@@ -115,13 +115,13 @@
find `pwd`/debian/tmp -type d -empty | xargs -r rmdir -p --no-fail-on-non-empty
</example>
-<sect1>Managing perl dependencies automatically
+<sect1>Managing Perl dependencies automatically
-<p>As you may have noticed, we do not have hardcored any specific
-perl version in the build process but the package may have to
-depend on a specific perl version (generally the version that has been
-used to build it). In order to never hardcore any perl version, we'll
-try to use a substitution. Instead to write "perl-5.005" or "perl5"
+<p>As you may have noticed, we do not have hardcoded any specific
+Perl version in the build process but the package may have to
+depend on a specific Perl version (generally the version that has been
+used to build it). In order to never hardcode any Perl version, we'll
+try to use a substitution. Instead of writing "perl-5.005" or "perl5"
in the control file we'll use "${perl:Depends}" and the build process
will add a line "perl:Depends=what_is_needeed" to the substvars file.
@@ -130,16 +130,16 @@
by adding the good lines in your rules file.
<p>If you want to know the version of perl that you're currently
-using for the build you can use something like that :
+using for the build you can use something like this :
<p><example>
version = `$(PERL) -e 'printf "%.3f", $$]'`
</example>
-<sect>Non-binary perl modules
+<sect>Non-binary Perl modules
<p>They must be installed in /usr/lib/perl5 and must depend on perl5.
-<sect>Binary perl modules
+<sect>Binary Perl modules
<p>They must be installed in /usr/lib/perl/$version/$arch-linux and
must depend on perl-$version.
@@ -149,35 +149,35 @@
can provide the threaded module in the same package or in another
package called libfoo-bar-perl-thread.
-<p>The binary modules must always be built with the latest perl
-available in Debian. You can build the module for an older version of perl
+<p>The binary modules must always be built with the latest Perl
+available in Debian. You can build the module for an older version of Perl
but in that case you must call the module package accordingly by
-specifying the perl version at the end of the package name
+specifying the Perl version at the end of the package name
(ie libfoo-bar-perl-5.004).
-<chapt>Packaging perl scripts
+<chapt>Packaging Perl scripts
-<p>This is very simple, perl scripts should always use /usr/bin/perl
+<p>This is very simple, Perl scripts should always use /usr/bin/perl
and should depend on perl5. At the present time you cannot setup
-a versionned dependency on perl5 as dpkg doesn't support this.
+a versioned dependency on perl5 as dpkg doesn't support this.
However you can be sure that perl5 is >= 5.004.05. If you really
need to make sure that you have perl5.005 then you should depend
-on perl-5.005 (and here you can use a versionned dependency). But
+on perl-5.005 (and here you can use a versioned dependency). But
you'll have to update your dependency when perl-5.006 comes out
and so on, so it's not very convenient.
-<p>Take care to include any dependency on a perl module as they are
+<p>Take care to include any dependency on a Perl module as they are
not automatically detected by the standard tools like the libraries
are. Lintian may warn you about such problems.
<p>If the script does have very special needs such as a specific version
-of perl then you'll need to use #!/usr/bin/perl-5.004 (I take 5.004 as
-an example but you should replace 5.004 by whatever old version of perl
+of Perl then you'll need to use #!/usr/bin/perl-5.004 (I take 5.004 as
+an example but you should replace 5.004 by whatever old version of Perl
you are needing) and you'll need to add a dependency to perl-5.004. If
it does furthermore request some binary modules then you'll need to
package thoses modules especially for perl-5.004 instead of
-the latest perl (beeing perl-5.005 or whatever else). Those
-modules packaged for old perls will have to add the perl version
+the latest Perl (being perl-5.005 or whatever else). Those
+modules packaged for old Perls will have to add the Perl version
in their package name. For a module Foo::Bar, instead of calling
the package libfoo-bar-perl you'll have to call it
libfoo-bar-perl-5.004.
- --
<torin@daft.com> <http://www.daft.com/~torin> <torin@debian.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI/Pilot programmer/tutor @
@ Make a little hot-tub in your soul. @
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.5.1, an Emacs/PGP interface
iQCVAwUBN3NhtY4wrq++1Ls5AQFi1AP/ctNJ83XocfvYH5yPK+Q4rCakfJSn/C7/
GsbKJGK3Xi/P3ISwm6Agbvf7X2Q/ODRUsikgEwyD+v+bMxeVkVJtigg50Do7g74f
spLViyM4EwTnHtX33gST/Pq9AigTX/xqitOztqSLxr0vJl2+XIXDihOcgw6N7OSW
/nqezMtjRR0=
=FWaa
-----END PGP SIGNATURE-----
Reply to: