Hi,

I'd like to ask for your advice or best practices regarding the package
structure of a project. So far I have understood:
- Iceberg can store multiple packages (project?) in a git repository
- A package (or multiple?) and its dependencies is loaded via a baseline
- A package can have flags (= categories?)

Suppose, a project has
- A core part
- One or multipel optional parts, that a user may or may not want to load,
too
- Tests for the core
- Tests for each optional part

What's the recommended way to structure this in Pharo? For example, I've
seen that some code in Pharo has its tests in the same package but
flagged/categorized, other code has a separate package for tests. Also, can
a (git) repository have multiple baselines?

Sorry, if I am asking the obvious but I did not manage to find guidlines in
the documentation yet. It might very well an oversight be myself.

Kind regards,
Steffen

Reply via email to