Mike Noyes wrote: > > On Wed, 2002-07-10 at 15:16, Michael D. Schleif wrote: > > > > Jeff Newmiller wrote: > > > > > > On Wed, 10 Jul 2002, 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.5/netsnmp.lrp ... > > > > devel/helices/net-snmp/v5.0.2/netsnmp.lrp ... > > > > > > This seems quite the wrong direction. CVS is supposed to manage > > > versioning completely independently of the directory structure. > > > > Yes, I agree. However, I am dealing with somebody else's software and > > making it suitable for leaf. Obviously, I can have several iterations > > of net-snmp v4.2.4 that address various leaf concerns. > > Michael, > CVS retains all previous versions of a file in the repository. You can > specify a specific version for retrieval. > > Example: > >http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/packages/glibc-2.0/dhclient.lrp > > Download version 1.10 > >http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/leaf/bin/packages/glibc-2.0/dhclient.lrp?rev=HEAD&content-type=application/octet-stream > > Download version 1.1 > >http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/leaf/bin/packages/glibc-2.0/dhclient.lrp?rev=1.1&content-type=application/octet-stream
Yes, these are our (leaf) _cvs_ versions. However, how can a user select net-snmp v4.2.4 when my net-snmp version is 1.1? > > What happens when I decide that /usr/sbin/ntp_setup actually belongs > > /usr/bin/ntp_setup? Or, /usr/sbin/ntp_setup becomes /usr/bin/setup_ntp? > > > > Clearly, cvs cannot know my intent, in this regard. When committing a > > directory change, under this scenario, how should it be done? > > If we had shell access to the repository, we would hand edit the > structure change. SF doesn't allow us shell access to the cvs server, so > we need to open SF support requests to make changes like this. If this is all that is available to us -- and, really, such requests seem to be available to only a few, like you, Mike -- then, it behooves me to select a good structure now, before I have to request alot of changes. That is why I belabor this point now. [ snip ] > > What should I, joe-leaf-user, expect to find while perusing ViewCVS? > > doc -- released documentation > bin/packages -- released packages sorted by library type/revision > > binary files for LEAF release/branch tree (write access controlled > by lead developer) > /bering > /dachstein > /oxygen > /packetfilter > /wisp-dist > /wrp > src -- source code Is that like Jeff's earlier directory structure outline, or is this referring to the text to include in the cvs commit blurb? > > I worry, however, if every developer goes about creating some adhoc > > structure to their liking . . . > > Think of the devel tree as individual repositories, and the doc, bin, > and src trees as community resources. Did that help? Right now, I'm only thinking about what goes under my devel/helices tree. How that gets tied into dcd, bering, or whatever, is another issue, which I've decided to ignore for the moment. Remember, this all started with your request to me to commit my net-snmp packages. I committed the LRP's only, and since I've begun to plan committing several other items. It's this planning that has me hung now; but, I'd really like to put that behind me ;> -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
