Hi elextr and anyone else who might choose to respond, hypothesize and or contribute to this thread. I appreciate (elextr) your response very much AND your responses is/are factual, useful information - Emphasis Added!! But at the same time you are not informing me beyond the boundary of my previously known information, my personal pre-existing knowledge base so to speak.
On the one hand, I cannot change how Debian aka Raspbian/Raspberry Pi chooses to allow its "decided upon" package manager "apt" to accumulate its allowable software versions, in the instant case here Geany 1.33, with A,B,C,D etc... dependent/requisite libraries in place. I really do not like fighting organizations (Debian in this case) to affect forward change - which I would likely have to do -to get Geany 1.38 as the basis for an actual Debian respository/repositories. On the other hand to seemingly satisfy Geany's Developers current requirements, this Geany user doesn't want to be - likely multiple, repetitive times - making, compiling, debugging, linking and copying files, installing requisite libraries ... manually - which by going step by step through the Geany 1.38 manual, you guys are suggesting I need to do to get Geany 1.38 working on this particular 32-bit Debian Buster 10 OS. And all to be lost/replaced upon a newer version of Geany becoming available. This means both proposed solution paths (Debian apt AND Geany Manual) are either impractical and or overly time consuming for this end-user and anyone else similarly faced, for a valid Geany 1.38 install. Proposed Solution Path 1: My particular forte on Linux is Python (it is a popular programming language these days), including issuing OS commands from a Python program and returning the results of those OS commands to Python - for evaluation and or further processing. I should in theory, for example, be able to auto-compile a C program by issuing a Python command (from a Geany edited+compiled Python pgm), and retrieve results on whether or not the Compile successfully completed and say output filename X.exe with a new creation date just successfully occurred, or not. If yes, automatically move on to next local Geany version 1.38 creation step. If not, find out why, attempt to "auto remedy" the situation, and repeat Compile/Make Geany 1.38 .Python program ... Proposed Solution Path 2: Use a "different" or "modified" Package Manager (not Debian repository "apt" per se, as is, standard) software tool - to attempt to get Geany 1.38 installed. For example: 5 Best Linux Package Managers for Linux Newbies: 1. DPKG – Debian Package Management System / APT (Advanced Packaging Tool) / Aptitude Package Manager or SYNAPTIC Package Manager - Synaptic is a GUI package management tool for APT based on GTK+ (like Geany) and it works fine for users who may not want to get their hands dirty on a command line. It implements the same features as the apt-get command line tool. 2. RPM (Red Hat Package Manager) / YUM (Yellowdog Updater, Modified) / DNF – Dandified Yum 3. Pacman Package Manager – Arch Linux 4. Zypper Package Manager – openSUSE 5. Portage Package Manager – Gentoo Source: https://www.tecmint.com/linux-package-managers/ Again, I am unable to use Debian's "apt" tool "as is" on this machine because "sudo apt update" and "sudo apt full-upgrade" do NOT currently update Geany to 1.38. Lacking input back from any of you, the Geany Development Team, or anyone else, I will likely first choose the Python solution path, not a standard app Package Manager per se (although Synaptic appears to have attractive attributes re Geany). I would prefer something that might best work long term. The Python solution is itself potentially problematic for other Debian Geany 1.38 installer-users since there are likely Python libraries installed on this machine that other Debian 32-bit OS's might not have installed. In summary, the task faced by this hopeful Geany 1.38 Debian Buster-10 32-bit OS user - is writing or implementing a custom Geany 1.38 Installer/Package Manager that ALSO attempts to locally compile using C / C+ / GTK requisite libraries - while also allowing for auto-downloading requisite libraries - as well as cleaning up after completion - and eventually uninstalling Geany 1.38 for a newer version or user dissatisfaction with Geany 1.38 itself. Any thoughts, suggestions, preferred solutions path(s), potentially helpful links to pursue, tutorials to check out, etc.? This is looking more and more like a long-term project, rather than a quick and easy fix/install. And like you guys, I have multiple other projects to pursue... “Optimism is a strategy for making a better future. Because unless you believe that the future can be better, you are unlikely to step up and take responsibility for making it so.” - Noam Chomsky, American Linguist Best Regards -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3502#issuecomment-1553330438 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/3502/[email protected]>
