Handbrake Guide wrote: the features you find in any open source software package are there because at least one programmer needed them and implemented them to meet their needs (more forward-thinking programmers often at least attempt to make them flexible enough to work for others with similar needs as well).
As a user I have a limited agenda. Having created a procedure that I need there are three options available:-
- Keeping it to myself
- Sharing it if it could be useful to others
- Promoting it, if possibility of others being bedazzled by its brilliance
First option excluded, as being not In conformance with spirit of 'giving back', sharing is the name of the game, promotion is not, as without tangible reward of some sort, it would seem in my book, to reflect needs of an ego trip.
Any procedure I put out to share, is along the lines of those automotive and bicycle workshops springing up these days, where all the tools are provided, but people have to get their hands dirty, there being always someone at hand to give advice on usage.
Last year pondering my experience with pkgs.org and what with necessity being mother of invention and all that, I realised it might be feasible to formalise, the manual method used before, as a procedure.
Oh! I see. These are promoting tools for your dependencies resolution strategies tools for pkgs.org.
I will come back to report on my dependency resolution for these two packages above gimp and fotoxx.
There is only one tool for pkgs.org. The other day I got so many small package dependencies that it crossed my mind to write these quick scripts, in a way anticipating a future demand should someone happen to use pakorg script. Anyway it's no skin off my nose if you don't use what's in front of your nose.
. As already mentioned it's a back burner project of mine, which I have gone to some trouble to bring to an almost finished state, in order to make available for general use to the Community. 8)
Having noticed in some posts on the forum, that some people were up against it in dependency searching, I made an effort to hurry up and get the procedure into a suitable state for testing, and then put it out there.
It was disappointing that those lamenting the lack of dependency solutions should completely ignore, not even cast a comment, on said procedure. It riles me when a certain someone complains about circular definitions in pkgs.org, as I have specifically stated that the procedure does away with circular definitions. However, as mentioned to Rava, there was the compensation of getting it ready for use far ahead of time, of seeing a concept working in practice, and to see that it actually delivered the goods.
What was really annoying was the fact that I had devoted all my spare time over a week to writing a description of the procedure, and had endeavoured to provide a step by step guide to its usage. Other than francois, not a peep from anyone else. No remark, good, bad or indifferent, just resounding silence.
There was a time when I could have done with help in testing, but that is long past. The main difficulty then, was trying to decide which similar sounding package/library could already be depended on as being on the system, and not having to be replaced. Managed that more or less by now, and when in doubt just replacing said package/library. Testing is long over, and as for 64 bit, not going to waste time over it.
Mon ami, I am not in the business of making a UNSM (Universal Non-Slackware Manager)
, and that is not to be expected of me. No Pie in the Sky for your humble servant. 8) However when I have created a procedure, which seemed to me could also be of use to others, I have given it a user interface and put it out there. If someone needs a module I make it if there are not too many dependencies (suppose if someone needs it badly could provide dependencies list)
. as it's a means of exercising my procedure.
I offer only 32 bit modules, as this favours older machines, thereby supporting resistance to the throwaway society. Someone with 64 bit system can always download a 32 bit iso and run app after launch from iso file, if they need it urgently enough, or install the libraries to run 32 bit modules, or actually use the procedure.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB