Re: [Leaf-devel] CVS structure ??? [LONG]
Ugh, I just reverted to the prior enforce script. I'll take a look at it again in the morning. Currently lowercase name enforcement is active. On Tue, 2002-07-16 at 17:12, Mike Noyes wrote: > Everyone, > I just removed the lowercase enforcement from our repository. If win > clients start leaving broken stub files in our repository, we'll need to > reexamine this issue. > > > On Thu, 2002-07-11 at 16:59, Mike Noyes wrote: > > On Thu, 2002-07-11 at 16:12, Manfred Schuler wrote: > > > You should not force all filenames (except Makefile) to lowercase. > > > Some kernel modules have uppercase letters in their names. > > > Also the README files are typically in uppercase. > > > An X terminal dist would have big problems with that rule. > > > > I believe this was done to address the following problem: > > Introduction to SourceForge.net Project CVS Services > > https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1 > > Case Sensitivity > > When a developer performs certain types of CVS operations, > > specifically "cvs add" and "cvs remove", CVS checks the listing > > of already-deleted files for that directory (i.e. the files in > > the Attic for that directory) to see if there is a match of the > > same filename. There is a difference between what MS > > Windows-based systems consider a match and what case-sensitive > > operating systems, such as Linux (which is used to provide the > > project CVS services), see as a match in these cases. If the > > filename match does not occur on the server, but there would be > > a case-insensitive match, the Windows-based CVS client will > > abort its operation and leave a broken stub file within the > > repository, which must be removed by SourceForge.net staff. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS structure ??? [LONG]
Everyone, I just removed the lowercase enforcement from our repository. If win clients start leaving broken stub files in our repository, we'll need to reexamine this issue. On Thu, 2002-07-11 at 16:59, Mike Noyes wrote: > On Thu, 2002-07-11 at 16:12, Manfred Schuler wrote: > > You should not force all filenames (except Makefile) to lowercase. > > Some kernel modules have uppercase letters in their names. > > Also the README files are typically in uppercase. > > An X terminal dist would have big problems with that rule. > > I believe this was done to address the following problem: > Introduction to SourceForge.net Project CVS Services > https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1 > Case Sensitivity > When a developer performs certain types of CVS operations, > specifically "cvs add" and "cvs remove", CVS checks the listing > of already-deleted files for that directory (i.e. the files in > the Attic for that directory) to see if there is a match of the > same filename. There is a difference between what MS > Windows-based systems consider a match and what case-sensitive > operating systems, such as Linux (which is used to provide the > project CVS services), see as a match in these cases. If the > filename match does not occur on the server, but there would be > a case-insensitive match, the Windows-based CVS client will > abort its operation and leave a broken stub file within the > repository, which must be removed by SourceForge.net staff. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS src tree structure
On Tue, 2002-07-16 at 14:05, David Douthitt wrote: > On Tue, Jul 16, 2002 at 11:38:49AM -0700, Mike Noyes wrote: > > > Both of these actions are performed using "import" from a directory > > outside of your checked out tree. > > Does this mean that I can't operate in the cvs checked out directory > structure until all directories have been imported? David, Not as far as I know, but a new check out is necessary if you want to modify any of the files in the newly imported tree. I usually delete my old local tree and check out a new one after imports. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS src tree structure
On Mon, Jul 15, 2002 at 10:28:00AM -0700, Mike Noyes wrote: > I think a system similar to "BSD Ports" or "Gentoo Portage" would be > great. David already has sample implementation available. > > http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/ Now I've actually (with Mike's help) been able to properly update this to reflect the current state of my ports configuration. Be aware that I must go over these again to refresh my memory and to update any thing that needs updating. That directory "archive" isn't supposed to be there; I'm going to try and delete it... Here is a portion of the comments from one of the Makefiles: # Standard makes # # make all -- the usual # make fetch-- get required tar files # make extract -- get and extract tar files # make patch-- get, extract, and patch source # make binary -- create binaries # make clean-- clean out working directory Things to do: * update the system so it uses a set of files pretailored for most configurations * further document files * update all Makefiles * dependency operations? Have one "port" check for another and do it if need be. Things like busybox (uClibc) could use this, but most things might not need it. One difficulty is not being able to "install" the code directly; perhaps this could be overcome with prefixes (PREFIX=xxx) and other such shenanigans. One make target I don't see would be "make package" (or "make lrp") which should probably be there --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS src tree structure
On Tue, Jul 16, 2002 at 11:38:49AM -0700, Mike Noyes wrote: > Both of these actions are performed using "import" from a directory > outside of your checked out tree. Does this mean that I can't operate in the cvs checked out directory structure until all directories have been imported? I'll try your instructions... --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] ppptd.lrp with bering rc3
Le Mardi 16 Juillet 2002 17:08, Stefan a écrit : > there seems to be a problem with rc3 and pptpd. i tested it with rc1 and it > worked. installed the same modules and the same patches (pppd). there are > no firewall-entries nor syslog-entries (allthough i put the debug-entry in > /etc/ppp/options & /etc/pptpd.conf & /etc/ppp/pptpd-options). any proposals > ??? > Hi Stefan: Could you describe the simplest possible setup working with rc1 and not working with rc3 so that I can try to reproduce your pb and see what I can do fo you ? I have never tried ppptd myself but I can learn... Jacques I have on my home network access to win98 or linux machines. --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS src tree structure
On Tue, 2002-07-16 at 11:15, David Douthitt wrote: > On Mon, Jul 15, 2002 at 10:28:00AM -0700, Mike Noyes wrote: > > On Sat, 2002-07-13 at 07:48, Mike Noyes wrote: > > > I will create this tree on Monday. However, this tree will need a > > > consensus on its structure before commits can begin. > > > leaf/src/packages > > > This is done. The floor is now open to propose structures for our > > src/packages tree. > > > > I think a system similar to "BSD Ports" or "Gentoo Portage" would be > > great. David already has sample implementation available. > > > > http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/ > > As Michael Schleif noted, I was only able to get the directory tree > and the top-level makefile. No matter what I did, I could NOT find > a way to: > > * add to CVS all directories and files recursively from a given path > on down. > > I also don't think I could even: > > * add to CVS a directory, including the directory and ALL files > contained within it. > > It appeared that I would have to add EACH and EVERY file ONE by ONE. David, Both of these actions are performed using "import" from a directory outside of your checked out tree. Example: $ cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf import \ -I ! "devel/yourname/newtree" vendor start Note: you must check out your tree after an import. An update will not retrieve the newly imported directory tree. http://sourceforge.net/docman/display_doc.php?docid=9960&group_id=13751 > I've a CD burnt with the "ports tree" (more of an Oxygen base source tree) > around here, and hope to get it into CVS with help... Maybe I should > upload it to my devel home directory I'll try to help where I'm able. I'd like to avoid placing more files on our SF shell server. We're already using ~900M. That's 400M than we're allocated. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS src tree structure
On Mon, Jul 15, 2002 at 10:28:00AM -0700, Mike Noyes wrote: > On Sat, 2002-07-13 at 07:48, Mike Noyes wrote: > > I will create this tree on Monday. However, this tree will need a > > consensus on its structure before commits can begin. > > leaf/src/packages > This is done. The floor is now open to propose structures for our > src/packages tree. > > I think a system similar to "BSD Ports" or "Gentoo Portage" would be > great. David already has sample implementation available. > > http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/ As Michael Schleif noted, I was only able to get the directory tree and the top-level makefile. No matter what I did, I could NOT find a way to: * add to CVS all directories and files recursively from a given path on down. I also don't think I could even: * add to CVS a directory, including the directory and ALL files contained within it. It appeared that I would have to add EACH and EVERY file ONE by ONE. I've a CD burnt with the "ports tree" (more of an Oxygen base source tree) around here, and hope to get it into CVS with help... Maybe I should upload it to my devel home directory --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] CVS structure ???
On Wed, Jul 10, 2002 at 01:14:07PM -0700, Mike Noyes wrote: > On Wed, 2002-07-10 at 13:01, Jeff Newmiller wrote: > > David Douthitt has advocated (and it sounds good to me but I haven't done > > it myself) a mechanism whereby sources obtained from other sources are > > kept in original form and a parallel directory containing patchfiles and > > compilation instructions is generated to allow LEAF-specific modifications > > to be maintained separate from the original source tree if > > necessary. Read the archives... :) > > Jeff, > David's Ports system for packages has my vote for our src/packages tree. > However, there may be problems with it that I'm unaware of, because I'm > not a programmer. > > Oxygen base in Ports form: > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/ >From having worked with FreeBSD extensively for several months now, I've been discovering more and more about the FreeBSD ports system that I like. I'll be revisiting the CVS tree and possibly updating it. I've been away for a bit, but hope to dive into active development soon. --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] [OT] Speaking of Licensing (2.nd try)
Something is definitely not right... I guess I have to talk to my ISP :( Anyway, I tried sending this yesterday, and since it hasn't shown up yet, I'll try once more: - Forwarded message from Jon Clausen <[EMAIL PROTECTED]> - Date: Mon, 15 Jul 2002 15:36:09 +0200 From: Jon Clausen <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [OT] Speaking of Licensing Mail-Followup-To: [EMAIL PROTECTED] Hi all All this talk about the different license schemes lately, has me wondering... What do I do with my blinder.lrp (it's getting closer to releaseability)... licensing-wise? The majority of the code is written by myself. But there *are* snippets of code here and there (mainly the C-parts) where I've basically cut/pasted and slightly modified examples I've found around the web... I'm not exactly sure if any *code* still survives, but in any case I've been looking heavily at some of the viewlogs etc. cgi-scripts that come with the weblet/bering-1rc2... I'll track down and ask the people who published aforementioned C-snippets, but what are my options/obligations in general? Does anyone have any good links on the subject? Personally I'd be only happy to see people using this thingie, but I would prolly be pretty upset if someone were to grab the code and advertise it as theirs... (not that I imagine anyone would *want* to do that since it's all still pretty sloppy/ugly anyway) I know this is slightly off-topic, but this is the only developer list I'm subscribed to, and as such I see this as my best bet at finding out about this... If this is inappropriate, please don't hesitate to let me know, alternatively reply by PM. TIA Jon Clausen P.s: I've now gotten a bit further with both the system itself, *and* the website: http://bund.dk/blinder/ if anyone's curious :) - End forwarded message - --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] ppptd.lrp with bering rc3
there seems to be a problem with rc3 and pptpd. i tested it with rc1 and it worked. installed the same modules and the same patches (pppd). there are no firewall-entries nor syslog-entries (allthough i put the debug-entry in /etc/ppp/options & /etc/pptpd.conf & /etc/ppp/pptpd-options). any proposals ??? greetz stefan --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] [OT] Speaking of Licensing
> All this talk about the different license schemes lately, has me > wondering... > > What do I do with my blinder.lrp (it's getting closer to > releaseability)... licensing-wise? Pretty much whatever you want :) > The majority of the code is written by myself. But there *are* snippets of > code here and there (mainly the C-parts) where I've basically cut/pasted > and slightly modified examples I've found around the web... > > I'm not exactly sure if any *code* still survives, but in any case I've > been looking heavily at some of the viewlogs etc. cgi-scripts that come > with the weblet/bering-1rc2... > > I'll track down and ask the people who published aforementioned > C-snippets, but what are my options/obligations in general? IMHO, writing code is a lot like writing books. Everyone copies everyone else's ideas, but you need to stay away from actually plagerizing something. Of course, trying to define exactly how much modification makes something entirely yours vs. a modified version of another author's code (or story, or whatever) is a pretty blurry line... > Does anyone have any good links on the subject? Saddly, no. Please share with the list if you find some good references. > Personally I'd be only happy to see people using this thingie, but I > would prolly be pretty upset if someone were to grab the code and > advertise it as theirs... (not that I imagine anyone would *want* to do > that since it's all still pretty sloppy/ugly anyway) Most of the open-source licenses are pretty strong about continuing to credit previous authors (one of the biggest sins in the open-source world is to deny credit to someone whose work you have built on). I doubt you found any major pieces of code that are reproduced in your new blind application (ie your work is basically original, not derrived), so you probably don't have to worry too much about licensing, but it would still maybe be nice if you included references to some of the material you used as references. Of course, if a big chunk of your code is lifted from somewhere, you will definately need to acknowledge that fact, and consider any licensing implications. BTW: I consider the weblet code (cgi-bin scripts) to be GPL'd, although there is no license specified. I guess I haven't worried about it too much because: - Adding licensing notices and author credits takes space, and I was trying to make everything as small as possible - I'm not particularly worried about recieving ongoing credit for the cgi-bin stuff...it wasn't that much work. - The shell-script stuff is pretty much open-source anyway...it's kind of hard to release a "closed-source" shell script :-) NOTE: There *IS* a GPL notification at the start of sh-httpd, it was a bit more work :) Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs commit directory structure ???
On Tue, 2002-07-16 at 06:52, Michael D. Schleif wrote: > > Mike Noyes wrote: > > > > On Mon, 2002-07-15 at 22:39, Michael D. Schleif wrote: > > > > > > No matter how hard I try, I cannot commit a directory structure to cvs. > > [ snip ] > > > I looked at your commit messages, and I think I understand what you were > > trying to accomplish. Here is a sequence that I believe would have > > worked. > > [ snip ] > > Is there some way to *transfer* a cvs module from my own cvs to > sourceforge/leaf cvs? Michael, Yes. A tarball of your current repository is needed for this. ref. # Introduction to SourceForge.net Project CVS Services Import of Existing CVS Repositories https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1 > I have created a cvs environment for my own development. Since I > already have [many of] my packages situated as local cvs modules, it > would be most convenient if there is some way to move modules from cvs_A > to cvs_B. CVS doesn't sync repositories. Either you use your local one or the one on SF. > Or, need I *export* a module from my own cvs prior to importing it into > sourceforge/leaf cvs? This is one method, but you'll lose your history doing it this way. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs commit directory structure ???
Mike Noyes wrote: > > On Mon, 2002-07-15 at 22:39, Michael D. Schleif wrote: > > > > No matter how hard I try, I cannot commit a directory structure to cvs. [ snip ] > I looked at your commit messages, and I think I understand what you were > trying to accomplish. Here is a sequence that I believe would have > worked. [ snip ] Is there some way to *transfer* a cvs module from my own cvs to sourceforge/leaf cvs? I have created a cvs environment for my own development. Since I already have [many of] my packages situated as local cvs modules, it would be most convenient if there is some way to move modules from cvs_A to cvs_B. Or, need I *export* a module from my own cvs prior to importing it into sourceforge/leaf cvs? -- 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: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs commit directory structure ???
On Tue, 2002-07-16 at 06:32, Michael D. Schleif wrote: > I now believe that all of my cvs study led me to conclude that I was > creating and modifying ``modules''; but, modules can only exist at the > top level under CVSROOT. Therefore, you are probably correct that cvs > import is the solution here. Michael, We have no modules defined at this time. If you would like a module defined, please send me the appropriate information for CVSROOT/modules. http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/CVSROOT/ > In an effort to correct my miscreant behaviour, I tried using cvs > remove. Under some conditions, cvs remove works as expected. However, > see failed transaction, at end, to see problems with inability to > generate locked files. I would need to see the commands you typed in to understand the lock file problem. It may have something to do with a prior command leaving your tree in an unstable state. > Are there limitations to cvs remove? What is the cause of the lock > problem? Yes. It will not remove directories. Again, I'm unsure. Would you post the commands you used? The information I'm working from is obtained from our leaf-cvs-commits list. http://www.mail-archive.com/leaf-cvs-commits%40lists.sourceforge.net/ -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] [OT] Speaking of Licensing
Hi all All this talk about the different license schemes lately, has me wondering... What do I do with my blinder.lrp (it's getting closer to releaseability)... licensing-wise? The majority of the code is written by myself. But there *are* snippets of code here and there (mainly the C-parts) where I've basically cut/pasted and slightly modified examples I've found around the web... I'm not exactly sure if any *code* still survives, but in any case I've been looking heavily at some of the viewlogs etc. cgi-scripts that come with the weblet/bering-1rc2... I'll track down and ask the people who published aforementioned C-snippets, but what are my options/obligations in general? Does anyone have any good links on the subject? Personally I'd be only happy to see people using this thingie, but I would prolly be pretty upset if someone were to grab the code and advertise it as theirs... (not that I imagine anyone would *want* to do that since it's all still pretty sloppy/ugly anyway) I know this is slightly off-topic, but this is the only developer list I'm subscribed to, and as such I see this as my best bet at finding out about this... If this is inappropriate, please don't hesitate to let me know, alternatively reply by PM. TIA Jon Clausen P.s: I've now gotten a bit further with both the system itself, *and* the website: http://bund.dk/blinder/ if anyone's curious :) --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs commit directory structure ???
I now believe that all of my cvs study led me to conclude that I was creating and modifying ``modules''; but, modules can only exist at the top level under CVSROOT. Therefore, you are probably correct that cvs import is the solution here. In an effort to correct my miscreant behaviour, I tried using cvs remove. Under some conditions, cvs remove works as expected. However, see failed transaction, at end, to see problems with inability to generate locked files. Are there limitations to cvs remove? What is the cause of the lock problem? Mike Noyes wrote: > > On Mon, 2002-07-15 at 22:39, Michael D. Schleif wrote: > > > > No matter how hard I try, I cannot commit a directory structure to cvs. > > > > I get lock failures, even when I try to commit them one directory at a > > time. > > > > Clearly, there is some approved process for doing this and I do not know > > what that is. > > Michael, > I looked at your commit messages, and I think I understand what you were > trying to accomplish. Here is a sequence that I believe would have > worked. > > >From a directory out side of your checked out cvs tree (devel/helices). > Create the directory hierarchy that you wish to add to our repository. > Then from inside the root of this new hierarchy execute: > > $ cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf import \ > -I ! "devel/helices/ntpclnt" vendor start > > Note: naming conventions aren't enforced on imports. > > Note: this command will not work now, as there is already a > directory with that name in our repository. > > Would you like me to open a SF support request, and have them clean your > devel/helices tree out? You can start fresh that way. Yes, have somebody purge/delete/remove devel/helices/ntpclnt and everything below that. [ snip ] # ls devel/helices/ CVS netsnmp.lrp netsnmpd.lrp nettrapd.lrp ntpclnt # cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf remove devel/helices/ntpclnt [EMAIL PROTECTED]'s password: cvs remove: warning: directory CVS specified in argument cvs remove: but CVS uses CVS for its own purposes; skipping CVS directory ? devel/helices/ntpclnt/package/ntpclnt.lrp ? devel/helices/ntpclnt/target/etc/ntpclient.conf ? devel/helices/ntpclnt/target/etc/init.d/ntpclient ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.bktype ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.conf ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.help ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.list ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.local ? devel/helices/ntpclnt/target/var/lib/lrpkg/ntpclnt.version cvs server: Removing devel/helices/ntpclnt cvs server: file `devel/helices/ntpclnt/readme.txt' still in working directory cvs server: Removing devel/helices/ntpclnt/package cvs server: Removing devel/helices/ntpclnt/target cvs server: Removing devel/helices/ntpclnt/target/etc cvs server: failed to create lock directory for `/cvsroot/leaf/devel/helices/ntpclnt/target/etc' (/cvsroot/leaf/devel/helices/ntpclnt/target/etc/#cvs.lock): No such file or directory cvs server: failed to obtain dir lock in repository `/cvsroot/leaf/devel/helices/ntpclnt/target/etc' cvs [server aborted]: read lock failed - giving up -- 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: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs commit directory structure ???
On Mon, 2002-07-15 at 22:39, Michael D. Schleif wrote: > > No matter how hard I try, I cannot commit a directory structure to cvs. > > I get lock failures, even when I try to commit them one directory at a > time. > > Clearly, there is some approved process for doing this and I do not know > what that is. Michael, I looked at your commit messages, and I think I understand what you were trying to accomplish. Here is a sequence that I believe would have worked. >From a directory out side of your checked out cvs tree (devel/helices). Create the directory hierarchy that you wish to add to our repository. Then from inside the root of this new hierarchy execute: $ cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/leaf import \ -I ! "devel/helices/ntpclnt" vendor start Note: naming conventions aren't enforced on imports. Note: this command will not work now, as there is already a directory with that name in our repository. Would you like me to open a SF support request, and have them clean your devel/helices tree out? You can start fresh that way. ref. CVS Setup - Importing Directories http://sourceforge.net/docman/display_doc.php?docid=9960&group_id=13751 Open Source Development with CVS - Starting A New Project http://cvsbook.red-bean.com/cvsbook.html#Starting_A_New_Project -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] cvs commit directory structure ???
On Mon, 2002-07-15 at 22:39, Michael D. Schleif wrote: > > No matter how hard I try, I cannot commit a directory structure to cvs. Michael, You need to use "import" to add a directory of files. You can use "add" to make new directories. > I get lock failures, even when I try to commit them one directory at a > time. Where in our repository are you trying to commit/add/import files? > Clearly, there is some approved process for doing this and I do not know > what that is. > > Also, what is this limitation that all files must use *ONLY* lowercase > letters??? This was explained recently. http://www.mail-archive.com/leaf-devel%40lists.sourceforge.net/msg05217.html -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
