[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: List of directories under a "top-level" module

From: chaitu
Subject: Re: List of directories under a "top-level" module
Date: Tue, 9 Sep 2008 07:51:01 -0700 (PDT)
User-agent: G2/1.0

Hi Todd,

Thanks a lot for responding. Here are my thoughts on some of the
things you said:

1. Under /src/abcd, I have a mix of files some of which are C/C++/PHP/
Perl code, PDFs (bulky), RPMs (bulkier) and MSIs (bulkiest). For
compiling my company's product, I need C/C++ code and for packaging, I
need some of the PDFs. But I don't really need the sub-modules
containing RPM and MSI files. Worst of all, the sub-modules keeps
changing from time to time so I cannot hard-code the list. I would
rather obtain a list of all sub-modules and filter out the names of
those bulky nasty ones and pass the rest to the checkout command. My
CVS is 1.11.17 which unfortunately doesn't support the 'ls' command
and the organisation is loathe to upgrade CVS :(

2. Ignorance of CVS is really the first thing to pop up in my mind
too, but then the higher management believes in doing fresh checkouts
blindly because on some occassions in the past, developers gained
access to the build machine (they are not supposed to, but thru social
engineering they could!) and changed certain source code files and
didn't bother to clean 'em up, causing merge issues. They instructed
us to check out code daily instead of disciplining the errant
developers. This is something I really cannot argue against as the
management in my company is not really any different than in those
around the world...........narrow-minded and afraid that anything new
or cool would break something somewhere.

3. I've even tried getting them to agree to shift the bulky ones into
a separate repository but they wouldn't listen.

Anyway, thnx for ur time once again. Hope I could make more sense to u
now. I am basically stuck in a place where I can't really do too much.
I'll read the link you've sent tonite.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]