[Lazarus] How to tell lazarus the location of a used package?

Mattias Gaertner nc-gaertnma at netcologne.de
Fri Nov 26 16:36:39 CET 2010

On Fri, 26 Nov 2010 16:01:45 +0100
Bo Berglund <bo.berglund at gmail.com> wrote:

> On Thu, 25 Nov 2010 21:05:48 -0500, waldo kitty
> <wkitty42 at windstream.net> wrote:
> >On 11/25/2010 06:09, Bo Berglund wrote:
> >>>> Now, the description on how packages work in lazarus leads me to
> >>>> believe that any given package can only exist in one single copy and
> >>>> this location is not inside the project code space.
> >>>
> >>> Each package/project should have its own directories. This ensures
> >>> that a package does not depend on a project, so it can work with many
> >>> projects.
> >>
> >> Not if they evolve and we must maintain old code when we need to
> >> return to an older time...
> >
> >isn't this what a versioning system is supposed to be able to take care of?? 
> >simply check out the old version and do what you have to do?
> That is exactly what a verioning system is for...
> But it also means that EVERYTHING that is used to create a particular
> software release must be grabbed from the versioning system and used
> by the IDE. In principle one test is to check out, then do nothing
> else than build the application. Next do a binary file compare between
> the newly built version and the one created at the time of the tag.
> If they are not binary the same then something has changed in the
> environment...
> One such thing is for example IDE specific stuff that works its way
> into the compiled binary. An example is what I have been saying about
> Delphi components that are integrated into the IDE but have changed
> from the time of the old code generation to now.
> If these components are not also grabbed on the same tag as everything
> else then we have a difference...

Same for FPC specific stuff, used third party libs and tools.
> In Delphi I solve this by not having global paths to the installed
> components, instead I add the path to each component that is actually
> used by the project to the project specific browse path list. And I
> use relative path specifiers.

You can do the same in Lazarus. As written three times. All good things
are three. So I give up here.



More information about the Lazarus mailing list