On Wed, Jul 10, 2002 at 02:19:58PM -0500, Michael D. Schleif wrote: >[1] Should I have separate trees for different underlying versions of >net-snmp? For example, I committed net-snmp v4.2.4. I am contemplating >building and committing both v4.2.5 and the totally different >distribution v5.x. So, one line of thinking is like this: > > devel/helices/net-snmp/v4.2.4/netsnmp.lrp > devel/helices/net-snmp/v4.2.4/netsnmpd.lrp
Looks good to me, would allow for recursive wget --no-parent or ncftp -R and version management would be a simpler. A copy of the current as devel/helices/net-snmp/current/netsnmpd.lrp or a zero legnth file devel/helices/net-snmp/current-is-v5.0.2 are also helpful; get devel/helices/net-snmp/current-* | sed | ncftpget -R v5.0.2 ><http://leaf.sourceforge.net/devel/helices/net-snmp/> presents several >TXT files that, once clicked on, present descriptive text regarding the >LRP's that reside in versioned directories below this one. Another >example is Jacques Nilo's <http://leaf.sourceforge.net/devel/jnilo/> >wonderful page that links to installation and troubleshooting >information. How are we to do this under cvs? I would put the txt files in the version directores for which they belong. At some point (maybe even by a cgi to select components) a custom disk image might be generated, such a program would have no trouble separating out .txt and .lrp files. // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:[EMAIL PROTECTED] File, Print, DB and DNS Servers. http://www.galis.org/george ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
