Mattias Gärtner schrieb:
Each package in the lazarus tree should have a unique name to not
confuse users.
You can have svn write access for a directory under components.
Hmm. Currently I have no installable components to offer, but it might
make sense to have an readily selectable docking manager component, or
preconfigured panels as docksites. For the name, dodi/ <g> or docking/?
BTW, components/README.txt is outdated :-(
The wording "Create standard package" suggests to me, that there can
exist non-standard packages - for what special needs? Perhaps two
entries should be provided, for component packages with IDE
integration, and runtime-only packages. The intial settings will
differ for both package types.
Where is this "Create standard package"?
Maybe it can be 'Create package'.
File -> New... -> Package
To make it clear:
It is not forbidden to put several packages/projects into one directory.
For example different versions or for test suites.
My problems possibly resulted from the immediate use of units in test
programs, whose output goes to the project directory, while the compiled
package output goes into the PkgOutDir, and the resulting duplicate
compiled files confused the IDE or the compiler.
When a package is created from parts of a project, the project should be
updated to use the package (Required Packages), and all the package
source files should be removed from the Project Files. Right?
DoDi
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
