Mark Goodwin wrote:
Hi Mark,
> Could you please send me a complete set of patches (against pcp-2.1.11-6)
> for debian. A while ago there was an SGI internal request for PCP on Debian,
> and so we might as well add a deb subdir to the build dir. Do you have
> code we can use to generate .deb packages?
I had a lot of patches to allow me to generate the .deb file
but I found a cool trick that allows me to not modify anything
in PCP (except for the rc-proc.sh file :-).
In fact, the install is totally done by the install-sh script,
and I noticed that it allows a DIST_ROOT environment variable
to be defined. So when I set this variable to the directory where
the package is being generated, all goes fine !
(most of the time, when you are at the TOP of the pcp package,
export DIST_ROOT=`pwd`/debian/pcp is fine).
> As a side note: how does your "PCP for Debian" differ from what might
> be produced by Alien (the package format converter)? See the Alien
> home page at http://kitenet.net/programs/alien/ for details.
I know alien. The difference is that RedHat based distributions
directories are not the same as the Debian ones. Another
point is that there are many tools that gives more power
to the user if he's on Debian. For example, Debian is using
a tool named 'debconf' that allows automatic installation
of a whole system (if properly configured).
Another point is that the installation procedure is
VERY different from A RedHat based one.
On RedHat (when I say RedHat, I mean, Redhat, Caldera, Suse,
Mandrake, etc.), the package gets installed without
any configuration of any kind. YOU have to configure
it after installation.
On Debian, the package manager (debconf is one part of
it) asks you several questions to know how it should
configure the program.
So the real difference is that after a package
installation ('apt-get install pcp' for example)
is done, on debian, the program is immediately
functionnal.
Another point is that on Debian, for one package, there
is one person that takes care of it. Most of the time
it's a person that uses the program, and likes using
it (for example, me :-). So he will know how the
program works, he will follow the discussions on
the mailing lists, and apply patches in case of
problems/security breaches.
That's one reason why a lot of admins prefer to use
Debian on servers. They know that package are well
maintained, and in case of bugs, they can file bugs
reports to the maintainer.
For example, for my part, if you try to install the
debian package you'll see some real differences between
an artificially converted package (with alien) and
a real native debian package.
When you install PCP, you will be asked if you want
a minimal protection for pmcd. If yes, he will ask you
the network to allow connections from.
By default, it will allow connections only from
192.168.0.* for pmcd access.
This is done throught debconf, and one of its interface
(noninteractive, text, dialog, Slang, web, gtk).
Slang is a new one (only available in the devel part
of Debian), it is really beautiful!
> > * I modified the rc-proc.sh to be compatible with
> > Debian (otherwise pcp won't start at all), without
> > destroying anything to keep compatibility
>
> OK, so this is at least one difference. I'll take this patch ..
I think it's the most important one (the only :-)
> > * About the weblog pmda, there is no manpage
> > for pmdaweblog, and /var/pcp/config/web is empty.
> > Is that normal ?
>
> No that is not normal. The RPM package installs the default config file
> /var/pcp/config/web/weblog.conf. Does your Debian package not install this?
> The missing man page is indeed a bug - I'll make a note to fix it.
Ooops, I haven't seen it. You're right, the Install works fine.
Luc Stepniewski
--
Luc Stepniewski <lstep@xxxxxxxxxxx> <http://lstep.free.fr/>
Adequat - Securite, Linux Public key: <http://lstep.free.fr/pubkey.txt>
Key D93B2D2D fingerprint = 49 00 CC D1 69 03 E2 94 C8 78 ED 3C 75 89 A8 DE
|