[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OOC Package Tool: Repositories
- To: ooc-list@informatik.uni-kl.de
- Subject: Re: OOC Package Tool: Repositories
- From: Ian Rae <ianrae@istar.ca>
- Date: Sun, 11 Apr 1999 20:28:47 -0400
- Delivered-To: jnzimmer@donau.informatik.uni-kl.de
- MMDF-Warning: Parse error in original version of preceding line at uklirb.informatik.uni-kl.de
----------
> From: Michael van Acken <acken@vanacken.do.uunet.de>
> To: ooc-list@informatik.uni-kl.de
> [..]
> With a repository, the placement of files is fixed. The files for a
> module `foo.bar.zap' can be found at these places:
>
> source file : <rep-root>/src/foo/bar/zap.Mod
> symbol file : <rep-root>/sym/foo/bar/zap.Sym
> object files : <rep-root>/obj/foo/bar/zap.*
> documentation: <rep-root>/doc/foo/bar/zap.html
>
These leads to foo's files being spread across five directories (including
_pkg). It would be "cleaner" to
put everything under <rep-root>/foo. This would also allow two packages to
have (unrelated) modules with the
same name without conflict. And it would allow two versions of the same
package to be installed,
presumably because some projects need the older version.
OOC already has a pretty good directory structure, but the repository idea
would generalize things nicely for
"user" code as well.
Cheers,
--Ian