On Tue, 2005-11-29 at 11:10 +0100, Thomas Anders wrote: > So, to double-check, you're preferring to: > - keep "dist" in CVS MAIN only *and* > - do not ship "dist" with the source distribution?
Yes - I think so. (but see below) The one thing that might be useful for the 'dist' tree of a patches branch is instructions for what might need to be changed from the MAIN version. (Or possibly the next main release branch). I take Wes' point about "would it be useful". But I think we need to balance the general usefulness of something against the effort needed to maintain it properly. For the core elements of the project, the general usefulness wins hands-down, naturally. But for something like this, which is mostly aimed at the core development team, it seems reasonable to put a higher priority on the ease of maintenance for us. > However, we will still need to ship some of the "dist" content > (net-snmp.spec, snmpd-init.d, snmptrapd-init.d) with e.g. source RPMs. Sure. So there might be a case for including those in the source tarball as well - I'm currently undecided. But we should probably try to keep the contents of this to a minimum. Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
