Re: [Nagios-devel] license status of contributed icons?
Posted: Sat Feb 19, 2005 12:31 am
--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
hi andreas,
On Fri, Feb 18, 2005 at 08:10:14PM -0800, [email protected]=
forge.net wrote:
> > 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). =20
>=20
> Oh. I thought it was something along the lines of a rpm .spec file. Do=20
> you mean dpkg doesn't have specifications at all?
what i was getting at is that debian doesn't use a single monolithic
file like the rpm "spec file" format. there's an entire subdirectory that
includes something kind of like a spec file (debian/rules) as well as many
helper files, patches, copyright info, and other debian-specific stuff.
with the way we've packaged nagios, everything you need to build a deb
is in this directory, though some other packages rely on an external
diff. so, you could check out a copy of the ./debian from our alioth
cvs repository, but like i said, i think it's inviting unnecessary
duplication of effort.
> nagios-statd is obsolete and shouldn't really be distributed by a=20
> dependency-handling package managing system.
fair enough. i'm not familiar with the package, but it came up with
the rest of the results from "apt-cache search nagios"
sean
--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCFvlKynjLPm522B0RAmInAJ4iXxKtSmFWD5D/t1MmxWObHbtGLgCghVfK
9LVTtHTTriwEBybVU9pIH98=
=X+NG
-----END PGP SIGNATURE-----
--SLDf9lqlvOQaIe6s--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
hi andreas,
On Fri, Feb 18, 2005 at 08:10:14PM -0800, [email protected]=
forge.net wrote:
> > 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). =20
>=20
> Oh. I thought it was something along the lines of a rpm .spec file. Do=20
> you mean dpkg doesn't have specifications at all?
what i was getting at is that debian doesn't use a single monolithic
file like the rpm "spec file" format. there's an entire subdirectory that
includes something kind of like a spec file (debian/rules) as well as many
helper files, patches, copyright info, and other debian-specific stuff.
with the way we've packaged nagios, everything you need to build a deb
is in this directory, though some other packages rely on an external
diff. so, you could check out a copy of the ./debian from our alioth
cvs repository, but like i said, i think it's inviting unnecessary
duplication of effort.
> nagios-statd is obsolete and shouldn't really be distributed by a=20
> dependency-handling package managing system.
fair enough. i'm not familiar with the package, but it came up with
the rest of the results from "apt-cache search nagios"
sean
--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCFvlKynjLPm522B0RAmInAJ4iXxKtSmFWD5D/t1MmxWObHbtGLgCghVfK
9LVTtHTTriwEBybVU9pIH98=
=X+NG
-----END PGP SIGNATURE-----
--SLDf9lqlvOQaIe6s--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]