Re: Changes in our .spec file

2008/5/6 Jan Safranek <jsafrane@redhat.com>:
> Fedora splits Net-SNMP to many subpackages....
> And another question is what about other distros - quick look at
> Mandriva shows, that they have completely different packaging of Net-SNMP.


Checking the "major" distributions (as listed in Wikipedia),
the main groupings seem to be as follows:

RedHat-esque
net-snmp{ , -devel, -libs, -perl, -utils}
Ark, CentOS, Fedora, RedHat, Scientific

Mandriva-esque
libnet-snmp{ N, -devel, -static-devel}
net-snmp{ , -mibs, -tkmib, -trapd, -utils}
perl-NetSNMP (?)
Annvix, Mandriva, PCLinux

SuSE-esque
net-snmp, net-snmp-devel
openSuSE, SuSE, Yoper


Plus two other single-distribution formats:
PLD: ucd-snmp{ , -devel, -libs, -snmptrapd, -statuc, -utils, -utils-perl}
ALT: lib{net, ucd}-snmp{ , -devel}, net-snmp-mibs, perl-Net-SNMP (?)


There seem to be some minor differences within these groups
(e.g. which types of library are packaged where), but the basic
contents seem fairly consistent.


> Second issue is that most distributions provide sample configuration
> file in /etc/snmp/snmpd.conf. Why don't we distribute one?

Mostly historical, I think.
The aim of our binary distributions has tended to aim for something similar
to the results of a simple
"configure ; make ; sudo make install"

That doesn't attempt to install any configuration files, so the binary
packages don't either. But it's perfectly reasonable to review both
aspects of that policy.

Dave

PS: Welcome!

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757...un.com/javaone
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders