Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi Gabriel- Ok, I understand that an import can be just an empty module and populated later, or it can be a module with content. Good. But is import the *only* way one should be creating a module (empty or otherwise). Tony, et al? Here's why I'm looking for answers... With the GUIs we use (SmartCVS and TortoiseCVS, btw), if a complete repository is checked out, the CVS folder is created where all of the modules are placed. If a CVS folder is created, both GUIs no longer provide the ability to import (or create) a "module" in that folder. They both expect you to add and commit the module there. If that CVS folder is *not* present in the directory where you hold all of those modules, both GUIs provide the "Import" (or make new module) function to create the module. Who cares? Well, if I want to control who can create modules, I was expecting to trap on the "import" command in the precommand trigger, assuming that import was always used to create a module. As my example above shows, sometimes it's import, sometimes it's add and commit, depending on how the folder was populated. Once the module is created, no problems, anyone can start filling it - I only want to control its creation. (I originally asked the SmartCVS team these questions but quickly found that this is CVSNT-related.) Much thanks for any clues, ronb > > >Is the "import" command the only way to create a module? > > I think so, but you don't have to actually import the module > contents. You can "import" an empty module, and then use "add" to > populate it. See the Chapter 4 on the CVSNT manual; btw, that's how > TortoiseCVS creates a new module. > > ____________________________________________________________________________________ Sponsored Link $420k for $1,399/mo. Think You Pay Too Much For Your Mortgage? Find Out! www.LowerMyBills.com/lre