Comment 34 for bug 275688
Revision history for this message
| Paul Gevers (paul-climbing) wrote Re: Please sync fpc 2.2.2-4 (universe) from Debian unstable (main) | #34 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
So far I have tested building 2.2.2-4ubuntu1 on gutsy, intrepid and hardy. Gutsy fails because of
Processing fpcsrc/
Error: Target "linux", package "fcl-base" not found
Googling for that error it looks like that is due to a different location of the fpc source [0]
Hardy and Intrepid build fine. See [1], including the logs.
I did not even start building on Dapper because the build depends are not fulfilled (fp-compiler, fp-units-base and fp-utils)
I am wondering thou, is this the way to go? Really trying to extract the relevant parts from the 2.2.2 version to patch the earlier releases is a bridge to far for me (with my current programming skills).
Should the Dapper and Gutsy version just be changed to reflect the change in licensing? How would we achieve this anyway? I guess than gearhead and python-soappy also need relicensing (how does that work? I that feasible?)
Although I am still willing to help, I could do with some more directions. I am pretty new to packaging (~3 packages) and am not really into programming. Rebuilding all the build depends in the different releases, right?
And just to be sure that I understand the situation:
All programs build with the old version of fpc can *only* be licensed under GPL (which version by the way?)
All programs build with the 2.2.2 version of fpc can be licensed under GPL or LGPL.
[0] http://<email address hidden>
[1] https:/