I think we should create different RPM's which all depend on eachother fpc-compiler…
This sounds ok but I also wish to have one monster get the whole deal at one shot RPM also...
Cliff

Mailing lists / lazarus / 1999-05
3 messages · 2 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
I think we should create different RPM's which all depend on eachother fpc-compiler…
This sounds ok but I also wish to have one monster get the whole deal at one shot RPM also...
Cliff
Thanx,
Looks like I will be doing alot of system reconfiguring tonight....
Once I get upgraded I will move lazarus to the 1.2 codebase.
After I complete this I am going to build a RPM that will install lazarus, fcl, compiler and the GTK. I will check everything for required files etc.
If I do this am I going to have to install to a different directory than FPC?
Should I keep our stuff separated, I think that I probably should to avoid conflicts. I can then control
what we are using to avoid compatibility problems. Lazarus will ultimately pass all the switches and paths to the compiler vs using the config unit because those settings are in the project file.
We probably should coordinate this with the FPC fellas. If I do this correctly it will allow easy setup
for someone who does not care to use lazarus but just want's the compiler.
Hopefully this will end most of the New User Problems once and for all....
Cliff
I think we should create different RPM's which all depend on eachother
fpc-compiler
fpc-rtl
fpc-fcl
fpc-gtk
and then you can depend lazarus on the needed rpm's. When everything works fine we can even create .rpm snapshots.
And .deb's ofcourse ;)
Except if they still choose to download the .tar.gz instead of the .rpm :)