Another solution would be to have a (possibly hidden) file within that
directory. My usual choice for such a file is .cvsignore since, presumably,
that directory won't remain empty which means you'll have to ignore files anyway
(of course, *.a, *.dll, *.lib, *.o, *.obj, and *.so are ignored by default
anyway).
Noel
[EMAIL PROTECTED] on 05/22/2000 10:19:25 AM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Noel L Yap)
Subject: Re: export "philosophy"
Kyle Hargraves writes:
>
> I'm not sure if this should be considered the correct behavior or
> not. The lib directory is in the repository, it's just empty. I'd
> rather not add a placeholder file, merely for aesthetic. Is there
> any ancient philosophy behind not exporting empty directories, or
> is this just a bug?
It's philosophy. CVS manages files, not directores. As far as it's
concerned, a directory is just a container for holding files so, if
there aren't any files, there isn't any reason for the directory. From
a pragmatic sandpoint, there currently isn't any way for CVS to
differentiate between a directory that's empty because all of the files
have been deleted and a directory that's empty because you really want
an empty directory. The usual advice is to have your build or install
procedure create the empty directory instead.
-Larry Jones
I always send Grandma a thank-you note right away. ...Ever since she
sent me that empty box with the sarcastic note saying she was just
checking to see if the Postal Service was still working. -- Calvin
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
