Subject | Structure of sourceforge repository |
---|---|
Author | Andreas Hesse |
Post date | 2009-05-23T10:27:07Z |
Here my proposal for the structure of the sourceforge svn repository:
-trunk
-<subproject name>
-source
-packages
-help
-demo
-test
-branches
-tags
where the names means following:
<subproject name> = name of (delphi) project
like iboadmin, ibovtree, ...
source = source code (*.pas, *.dfm, ...)
packages = delphi package (*.dpk, ...) files
help = help source code, compiled help file
demo = examples
test = test files, unit test for the project
If this structure is ok, I will check in iobadmin, ibovtree, native
ibo components for fastreport and shortly fbconsole as a D2009
successor of iboconsole.
Regards,
Andreas
-trunk
-<subproject name>
-source
-packages
-help
-demo
-test
-branches
-tags
where the names means following:
<subproject name> = name of (delphi) project
like iboadmin, ibovtree, ...
source = source code (*.pas, *.dfm, ...)
packages = delphi package (*.dpk, ...) files
help = help source code, compiled help file
demo = examples
test = test files, unit test for the project
If this structure is ok, I will check in iobadmin, ibovtree, native
ibo components for fastreport and shortly fbconsole as a D2009
successor of iboconsole.
Regards,
Andreas