Component installation (Feature request) #636
Comments
|
Some years ago, I have disabled the option to install multiple modules at once. Due to the fact that it gave too many install errors that were hard to track. |
|
That could work, but it wouldn't be ideal. I always have a bad feeling when I have to tinker with ini files whose versions can easily change.
That's why I have an extra file in my programs for such purposes. It either exists, in which case it is also read in, or it is not.
This would also improve handling, because only this one file would have to be copied into the installation directory.
It would also be easier for you if you didn't have to take this into account when you have to introduce new settings in fpcup.ini.
To deal with the mentioned installation errors:
it might be a good idea to mark the function as experimental or only allow the file to be read if it exists. Or hide the function in a context menue (as OPM does)
For my purposes i'd like to install components which are not supported by OPM (eg messagecomposer, Todolist etc)
Gesendet: Samstag, 11. November 2023 um 09:12 Uhr
Von: "Don" ***@***.***>
An: "LongDirtyAnimAlf/fpcupdeluxe" ***@***.***>
Cc: "CharlyTango" ***@***.***>, "Author" ***@***.***>
Betreff: Re: [LongDirtyAnimAlf/fpcupdeluxe] Component installation (Feature request) (Issue #636)
Some years ago, I have disabled the option to install multiple modules at once. Due to the fact that it gave too many install errors that were hard to track.
However, it might be an idea to re-introduce it. Will think about it.
In the meantime. If you change your own fpcup.ini: module "MyOwnModule" and add the desired modules. Does that work for you ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Ok Implemented. How it works. |
|
Thanks for implementing this feature.
Works quite well.
I hope this is not presumptuous, but I would like a description that at least describes the INI file a little. Especially the optimization of the complete compile runs would be interesting, because obviously one run per module section happens at the moment
Regards
Gesendet: Samstag, 11. November 2023 um 16:16 Uhr
Von: "Don" ***@***.***>
An: "LongDirtyAnimAlf/fpcupdeluxe" ***@***.***>
Cc: "CharlyTango" ***@***.***>, "Author" ***@***.***>
Betreff: Re: [LongDirtyAnimAlf/fpcupdeluxe] Component installation (Feature request) (Issue #636)
Ok Implemented.
87cb49f
The binaries have been updated
https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/tag/v2.4.0bp
How it works.
The new binaries will create a new file : defmods.ini
Edit it to fit your needs.
Run fpcupdeluxe again and it will use this file.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apparently fpcupdeluxe has the ability to install several components in a single run.
Example: fpcup.ini -> [FPCUPModule0]
Is it possible to to provide a funktion to install all needed components after download and compilation similar to OPM and Docking.
This way components not supported by OPM could be installed in a conveniant way.
I don't know how much work this is and whether it is even possible. But transferring settings in an old Lazarus to a newly installed instance would be the icing on the cake.
PS: Thank you for your work. Just the possibility to install Lazarus in this form is an argument to use Lazarus instead of D.
The text was updated successfully, but these errors were encountered: