sean finney wrote:
> hi andreas, gary,
>
> On Thu, Feb 17, 2005 at 08:17:28PM -0800, [email protected] wrote:
>
>>Message: 2
>>From: "Cook, Garry"
>>
>>Mine should be considered GPL (Cook logos). I think that I submitted
>>them with a README stating this, but that was a while ago, hard to
>>remember. Perhaps it's time for an update.
>
>
> great, thanks a lot for clarifying that. we've been wanting to
> have a nagios-icons package for quite some time now, and this
> is definitely a step in that direction.
>
>
>>From: Andreas Ericsson
>>The licensing depends on where you are. Most countries have amendments
>>to their copyright laws preventing person a to profit from person b's
>>work of art without paying royalties, meaning you can't sell the logos
>>explicitly or include it in a product in such a way that it
>>significantly raises the market value of that same product.
>
>
> ...unless they explicitly allow that with via a free software license
> allowing unlimited redistribution, such as the GPL. this is exactly
> why i'm trying to get a clarification on these terms from the authors.
>
>
>>This assumes there's money involved ofcourse, so I don't think the
>>Debian project is in any real danger.
>
>
> actually, if people were not allowed to redistribute the icons for
> profit, it could not be included in debian. take a look at clause 1 of
> the debian free software guidelines[1] to see what i mean.
>
>
>>Btw, when you're done with the .deb, would you mind uploading the
>>.spec-file equivalence to be included in the distro dir of Nagios?
>
>
> the spec file equivalent would be a ./debian subdirectory, and possibly
> patches to the source (though our custom with the current nagios
> packages is to have the diffs embedded in ./debian).
>
> however, keeping a debian directory in sync with what's actually
> in debian might be more hassle then it's worth. if you really want to
> do this, we'd need to work out the logistics.
>
Oh. I thought it was something along the lines of a rpm .spec file. Do
you mean dpkg doesn't have specifications at all?
> it would probably be best to have a README.Debian in this distro
> directory which says something like
>
> ================================================================================
>
> for the 1.x series of nagios, there are three different nagios packages
> available, which use different backends for storing information:
>
> nagios-text
> nagios-mysql
> nagios-pgsql
>
> for the 2.x series of nagios (proper information supplied here when
> we figure out what we're actually going to do).
>
> to install one of these on your debian system, do:
>
> apt-get install nagios-text
>
> (assuming you want the first option)
>
> if you would like to create your own debian package, make sure you have
> a deb-src line in /etc/apt/sources.list and get started with the
> following command:
>
> apt-get source nagios
>
> you may also want to consider installing these other nagios related packages:
>
> nagios-plugins - Plugins for the nagios network monitoring and management system
> nsca - Nagios service monitor agent
> nagios-nrpe-plugin - Nagios Remote Plugin Exectutor Plugin
> nagios-nrpe-server - Nagios Remote Plugin Exectutor Server
> nagios-nrpe-doc - Documentation for nagios-nrpe
> nagios-statd-client - nagios client for montioring remote system information
> nagios-statd-server - nagios server for monitoring remote system information
> nagat - Nagios Administration Tool
>
nagios-statd is obsolete and shouldn't really be distributed by a
dependency-handling package managing system.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Lead Developer
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]