Hey there peeps… 🙂
Another day, another wtf story on my beloved penguin..
So, I had APC Smart-UPS SC 620 for very long time and just now I had bravery to try to make some use of it and use it in Smart way. But then the crap started to make its shape all over the horizon.
First of all – all installation is flawless. But is misses some normal MAN here, so I will try to summarize everything in one single blog/spam/post.
The Linux Mint description of package: http://community.linuxmint.com/software/review/apcupsd
The Ubuntu Community info: https://help.ubuntu.com/community/apcupsd
The tutorial for using CGI: http://www.techrepublic.com/blog/diy-it-guy/diy-enable-cgi-on-your-apache-server/#postComments or http://www.fiz-ix.com/2012/12/configure-apache-mysql-and-cgi-bin-on-an-ubuntu-lamp-server/
To get this damn CGI, I had to:
- Read Apache2 config and adjust correct syntax for ScriptAlias and Directory ; Also find out that I had to use
Require all granted instead of old ( v2.2 premission granting syntax ).
- And use this command:
sudo a2enmod cgi
My issue: http://stackoverflow.com/questions/21352218/apcupsd-not-respecting-timeout-in-linux-mint-16-petra-x64
Well… again…some time since last post…
What was in my focus recently was some optimizations of what I do and how I do stuff and eventually found same real gaps between expectations and reality.. what a surprise, ai’? 🙂
So… here is one interesting blog post:
Well … It caught my eye because of the project I assisted a bit recently …
And was curios for the options to have such tests running within CI infrastructure.
Other activities, you may ask … well, there is this petition:
… which is just as irreveleant as it can be… no one seems to care anymore of such things big Corps do .. 😦 Of course – end user has no way to influence this situation also.
If I will get other insights of my time wasting life fiving approach, I will spam… here, most likely. 🙂
Hm,. Yes – remembered – I just updated my LinkedIn profile. 🙂
During my time using NSIS, there is these things noticeable:
I have found out that nothing is more powerful than parsing !verbose 3 level output with self-made tool 😉
I have found out that you can NOT depend on any NSIS-based debugging method. It may crash .. and your installer will crash along with it. No pretty, eh’? 😦
I have found out that enabling/disabling debugging on-demand is also very powerful weapon against idsses as it allows to distinguish between unstable and failed NSIS build ( it is easier to use CI terminology though… 🙂 ).
I have found out that verbose output w/o realtime automated NSIS testing is like driving Cadillac with bicycle engine 🙂
Hope it helps for those accidentally visiting this question 🙂
EDIT: It’s always good idea to start with 3rd party tools. For example, no need to hassle around GUI as it is always easier to use tools like:
EDIT #2: I have found out that pretty effective method for debugging is to use direct documentation automatization. Currently I use the following components:
The result is that I got screenshot after nsDialog:Show plus I got updated images in wiki 🙂 .. only stuff left is to fetch info from svnlook 🙂
EDIT #3: And the need of svnlook is also worked-around by building a svn log –xml exporting DLL using NSIS v2.44 header for Delphi and Lazarus IDE 0.9.30.2 🙂 Kudos to Lazarus!
>>> Original post @ SO: http://stackoverflow.com/questions/1630841/methods-for-debugging-nsis-installers/10087385#10087385