Thomas Anders wrote: > My initial list of distros that *I* am sort-of-supporting (i.e. provide > packages for via the openSuSE Build Service) is here: > > http://www.net-snmp.org/wiki/index.php/Third-Party_Packages
During the monthly administrative meeting we agreed: - the [above] list looks a reasonable starting point (?maybe plus Mandriva?) - we want one big package + separate -perl and -devel, as it is now, + proper Conflicts: and Provides:, tailored to as many distributions as we can. That means somebody (I volunteer for RHEL and Fedora) will check current .spec in SVN, add proper Provides:, Conflicts, BuidReqs (with ifdefs where needed) and ensure it works on a distro. Following needs more discussion here: I proposed to split net-snmp packages for long-supported distros (SLES and RHEL having in mind) to fully replace the native ones (i.e. have separate .spec file and packages net-snmp/-utils/-devel/-perl/-libs for RHEL), so we won't force user to install all dependencies if he/she wants to use only one package. IMHO it's not much effort, just create new .spec each ~2 years when new version comes and occasionally watch for rebase. Several concerns were raised: > it's a work and split effort Yes, it is. I volunteer to do the .spec and tracking for RHEL. > What if the net-snmp changes, should we then chage the RHEL.spec? > then it won't mirror RHEL any more. Then what is the point? If we significantly change net-snmp, we will probably change also version number and soname and RHEL users can't use the new version anyway. They will need to stick to old version. RHEL5 users must use 5.3.x branch, RHEL4 5.1.x or they have to recompile lot of packages or install it somewhere else (-> don't replace native packages and we don't need to care about it). > Who are professional [long-supported distros]? Should we track > Ubuntu? Oracle? Why not, if somebody volunteers. If not, then don't track them. > How does this compare with what Jan/Thomas already have > for the openSuSE builds? The build service is a repository of many .spec files, each distro and net-snmp branch having it's own one. I.e. there is separate net-snmp-5.3-snapshot-CentOS_5.spec, net-snmp-5.3-snapshot-Fedora_7.spec, net-snmp-5.3-snapshot-RHEL_5.spec, net-snmp-5.3-snapshot.spec (for openSUSE) + the same for 5.2, 5.4 and HEAD branches, 29 spec files together (!). These spec files are derived from the SVN ones and many of them are the same. Occasionally they are tailored to build on the appropriate platform (i.e. added/removed BuildRequires). I don't know how building for Debian and Ubuntu works, I noticed only one debian.tar.gz for each branch. The buildservice takes the specs and SVN snapshots of every branch and builds nice set of packages, available at WIKI or http://download.opensuse.org/repositories/net-snmp/ Jan ------------------------------------------------------------------------- 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;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
