[Lazarus] fppkg and lazarus packages

Joost van der Sluis joost at cnoc.nl
Fri Sep 3 11:08:30 CEST 2010

On Fri, 2010-09-03 at 09:58 +0200, Graeme Geldenhuys wrote:
> Op 2010-09-02 22:05, Joost van der Sluis het geskryf:
> > >
> > > fppkg update
> > > fppkg install lnet
> > >
> > > Check if everything is ok with 'fppkg list'
> I get the following error. I've got latest FPC 2.4.3 in my path under
> 64-bit Linux.

This (the lazarus addition) only works with 2.5.1. I'll merge it to
2.4.3, but only after I'm sure it won't end up in 2.4.2 at some manner.

> ------------------------------------
> ~ $ rm -rf ~/.fppkg
> ~ $ fppkg update
> ~ $ fppkg list
> Name                 Installed        Available
> lnet                 -                0.6.4-2446
> ~ $ fppkg install lnet
> The FPC Package tool encountered the following error:
> [lnet] Package fcl-process <none> is not available
> ------------------------------------

This has nothing to do with 2.4.3, but that you have your
fpc-installation in a non-default path and fpcsrc not set. (guess, it
could also be a bug)

Please set the prefix in the configuration-file to the right value, but
on 2.4.3 it will be called BaseInstallDir. (~/.fppkg/config/default)

Then try again. 

If this doesn't work try 'fppkg list -v' and see what happens. 

> BTW:
> How can we publish our own package to that list produced by 'fppkg list'. I
> have been wanting to add fpgui to that list since fppkg came to be.

hmm. didn't thought of fpgui.

> I think the whole fppkg concept is great (almost like perl's CPAN concept).
> Unfortunately they FPC rollout of this feature (fppkg and fpmake.pp) is so
> slow - nearly useless. :-(

Yeah, I think it's a better approach to add third-party packages and
maybe move some packages from fpc to this third party packages and let
the system mature.

Then later on we can switch parts of fpc itself.


More information about the Lazarus mailing list