On Sat, 2 Dec 2000, Luc Stepniewski wrote:
>
> I updated the debian package for PCP to work with
> PCP 2.1.11.
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?
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 modified the rc-proc.sh to be compatible with
> Debian (otherwise pcp won't start at all), without
> destroying anything to keep compatibility
> with other platforms (tests with /etc/debian_version
> to see if we're on a debian box).
> I've used the update-rc.d debian tool to update
> the links which is a lot easier than doing symlinks
> everywhere :-)
OK, so this is at least one difference. I'll take this patch ..
>
> * The Apache pmda is functionnal
Michal has suggested a small patch to allow Apache PMDA to build
in the case where PCP is not installed on the build machine.
>
> * 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.
>
> What is the current status about adding the debian/
> directory to official distribution ? The last time
> I asked you told there was a legal discussion about
> this. Has this been solved ?
Yes it has been solved in the least painful way we could think of.
If you want to contribute a stand-alone piece of code (e.g. apache PMDA
is a good example), you can request it be placed in the pcp contrib area
[surf to ftp://oss.sgi.com/www/projects/pcp/download/contrib to view
the legal conditions for doing this].
If you want some code written by you to be included in the base PCP
distribution, the easiest method is to literally give the source and
copyright to SGI.
If that doesn't fit with your requirements, you can retain copyright.
For example, read the copyright notice in pcp-2.1.11-6 or later in the
file src/libpcp_http/src/http_lib.h
In both cases, you'll have to formally agree to some legal stuff via email
(mostly to confirm that you are the sole author of your contribution). It
might sound complex and painful, but it's really not at all.
thanks
-- Mark
|