Forum > Packages and Libraries

TCustomShellTreeView.GetFilesInDir() in KASComp package

<< < (2/2)

wp:

--- Quote from: Chusik on December 02, 2023, 12:35:21 pm ---OPM contains a very outdated KASComp version.

--- End quote ---
It is a bit unusal that the KASToolbar package used by the project has a dependence of the project-specific package doublecmd_common. This means that everybody who wants to include KasToolbar in his own project must also install this package. I did not find anything about whether KasToolbar is a third-party packages for doublecmd, or whether it was written specifically for doublecmd. In any case, general usage of KasToolbar is limited due to this dependence - I would not think of using KASToolbar in any of my projects because it would require having doublecmd (or at least part of it) on my system...

Alexx2000:

--- Quote from: JuhaManninen on December 02, 2023, 02:40:27 pm ---Maybe Double Commander developers should push maintainers of the required packages to get the packages updated in OPM instead of copying them into DC sources.

--- End quote ---
Double Commander included in the several Linux distributions. So it must compilable out of the box without user interaction.
Most of packages included into Double Commander is maintained by me or have a specific patches.


--- Quote from: wp ---It is a bit unusal that the KASToolbar package used by the project has a dependence of the project-specific package doublecmd_common.

--- End quote ---
KASToolbar is written by me specially for Double Commander. Really doublecmd_common is a general purpose package, it does not have a project-specific only stuff.

JuhaManninen:
OK.
In any case Double Commander is a nice file manager. For some reason I have not used it much. I mainly use KDE's own Dolphin.
I will use Double Commander more for real action in the future.

wp:

--- Quote from: Alexx2000 on December 03, 2023, 01:28:12 pm ---
--- Quote from: wp ---It is a bit unusal that the KASToolbar package used by the project has a dependence of the project-specific package doublecmd_common.

--- End quote ---
KASToolbar is written by me specially for Double Commander. Really doublecmd_common is a general purpose package, it does not have a project-specific only stuff.

--- End quote ---
Sorry, this was not meant to be some kind of criticism. Just built the Double-Commander, and I see that it is an amazing product!

But one question: you mention that some third-party packages "have a specific patches". Which effect does this have on my system? For example you include a v3.1 of DCPCrypt while the version distributed by OPM is v2.0.4.2. It is a problem in the Lazarus package system that only a single package can exist within the IDE. So, when I write an application needing DCPCrypt I will be using your version after I compiled Double-Commander, and maybe use features which are not available in the "normal" version 2.0.4.2, and when I publish my application as open source users may not be able to compile it because they cannot resolve this dependence (and even I myself may have forgotten about it).

Therefore my suggestion: Rather than adding these modified third-party components to your project as packages could you just set the unit path of the project to point to them. Of course, components in these packages must be created at runtime then. This way a user could use a modified package in addition to an already installed package.

Alexx2000:
I think I should to rename DCPcrypt in Double Commander sources. It contains many changes. So it will not conflict with original version.

GifAnim in OPM already contains an old version from Double Commander. So it can be updated in OPM from Double Commander sources. As I know it is not maintained by original author.

Navigation

[0] Message Index

[*] Previous page

Go to full version