[Lazarus] Create a package - how?

[Mattias Gaertner]

On Sat, 06 Jun 2009 07:26:46 +0200
Hans-Peter Diettrich <DrDiettrich1 at aol.com> wrote:

> 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 :-(

I updated some parts.

 
> >> 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

Add ons can register other package types there.

 
> > 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.

Yes, it's confusing for the IDE, the compiler and the developer.
The IDE should check and warn if source directories are shared. Not only
via the test function, but before every compile. It's a todo. You can
create a feature request, so it won't be forgotten.

 
> 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?

Yes, and the IDE should tell the user about the move. It's a todo. You
can create a request too.

Mattias