Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2007-08

fpmake manifest question

4 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Darius Blaszijk

When looking at the manifest I came across some variables that are not stored in the manifest file. Are these decided to be not in, or do they need to be implemented?

Directory (is this the package installation directory, what about platform dependence?)
License
Options

Are there any others?

Darius

Reply by email

Michael Van Canneyt
to Darius Blaszijk
Darius Blaszijk wrote 6 lines
When looking at the manifest I came across some variables that are not stored in the manifest file. Are these decided to be not in, or do they need to be implemented? Directory (is this the package installation directory, what about platform dependence?)

Is not important. fppkg will know the directory.

License

This could be stored. Not the whole license (understand: the complete LGPL text or so), but a single sentence describing the type of the license.

Options

They don't need to be stored, as fpmake contains them.

Are there any others?

I think not.

Michael.

Reply by email

Darius Blaszijk
to Michael Van Canneyt
Michael Van Canneyt wrote 14 lines
On Wed, 15 Aug 2007, Darius Blaszijk wrote: > When looking at the manifest I came across some variables that are not stored > in the manifest file. Are these decided to be not in, or do they need to be > implemented? > > Directory (is this the package installation directory, what about platform > dependence?) > Is not important. fppkg will know the directory.

OK.

Show quoted text 6 lines
> License > This could be stored. Not the whole license (understand: the complete LGPL text or so), but a single sentence describing the type of the license.

The license property is just a string type. Anyone can put in anything he/she likes. I would also prefer only a simple description, but there is no way to prevent whole licenses with the current implementation.

Show quoted text 11 lines
> Options > They don't need to be stored, as fpmake contains them. > Are there any others? > I think not.

Fine, then please consider the following patch.

The patch additionally has:

- FPC version is not initialized to 2.0.4 by default but takes the FPCVERSION include
- Fixed TPackage.GetFileName when no version is set

Darius

Reply by email

Peter Vreman
to Darius Blaszijk
Show quoted text 7 lines
Fine, then please consider the following patch. The patch additionally has: - FPC version is not initialized to 2.0.4 by default but takes the FPCVERSION include - Fixed TPackage.GetFileName when no version is set

Applied, thanks.

Peter

Reply by email