On Mon, 20 Aug 2007, David Lyon wrote:
> Marco van de Voort wrote:
> > > > Define "load". Also keep in mind that Perl installs interpreter
> > > > sourcecode, what exactly do you imagine for FPC? compiled libs, source?
> > > > How do you deal with versioning?
> > > >
> > > >
> > > Right. That's what perl does. We should do the same thing. Then compile it
> > > into a library that we can use.
> > >
> >
> > I don't understand what you really want to add. The perl reference is next
> > to useless. Please be more descriptive.
> >
> The typical scenario is this... need a library for say ... blowfish
> encryption...
>
> Run the package-manager fppkg ... search for blowfish... find the package...
> download it... compile it... and have it available.
>
> we end up with the following files in our directories...
>
> /packages
> /source - blowfish.pas
> readme.txt
> moduleinfo.xml
> /library
> blowfish.dll
> (or) blowfish.so
or
/units/blowfish.ppu
That is what is implemented now. There is no need for the library.
If you start with libraries, then they must be deployed as well, and that
will start nameclashes, version clashes etc. This is avoided with the units.
>
>
> > > The issue is more about platform independance and download size. By
> > > distributing packages in source code and compiling them after download, it
> > > means quicker downloads and less time recompiling the whole of lazararus
> > > just to add in a new package.
> > >
> >
> > How is this different than e.g. fppkg ?
> >
> Things we need to look at :
>
> - a central code/libary repository ie like cpan
That is already implemented in fppkg.
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
