[openbeos] Re: CVS question
- From: "Marcus Overhagen" <dos4gw@xxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 31 Oct 2001 15:04:52 +0000
Michael Pfeiffer <michael.pfeiffer@xxxxxxxxx> wrote:
>AFAIK you can not remove directories with cvs.
>You can specify a command line option to cvs when you checkout
>files that it should not check out empty directories.
Hm, that's bad. I also created a directory. But luckily not in the root.
We have to reconsider the CVS structure anyway.
Where do we put the headers?
How do we separate public headers from those needed
by inter kit communication? for Example, the new
media_server needs to communicate with libmedia.so
Where do I put this header files?
Then I have some header files that are not binary compatible
with the BeOS R5. I don't want to mix them in between the normal
headers. So wherre do we put them?
do we make a new root headers directory, for example similar
to /boot/develop/headers/be?
Example:
For the binary compatible headers for use by applications & add-ons
/headers/public/be/game/
/headers/public/be/midi/
/headers/public/be/media/
/headers/public/be/kernel/
/headers/public/be/storage/
/headers/public/be/support/
/headers/public/posix/
/headers/public/cpp/
/headers/public/gnu/
For the headers used internally by the kits
/headers/internal/be/game/
/headers/internal/be/midi/
/headers/internal/be/media/
/headers/internal/be/kernel/
For the headers that are breaking compatibility and are still experimantal,
for example the non working media Decoder / Encoder headers
I tried to reverse engineer
/headers/experimental/be/game/
/headers/experimental/be/midi/
/headers/experimental/be/media/
Just as a suggestion. But we need to organize it somehow!
Other related posts:
