Re^3: How start an application on Linux

A matter of taste ;-) But i think it should be installed in /usr/local/bin or perhaps /opt/bin.

Keep in mind that it is always good practice to leave system Perl untouched.

And IMHO you should have access to a Linux box and test the install routine also there.

Please see also Filesystem_Hierarchy_Standard.

Update:

The paths you mentioned should be in the PATH environment variable under normal circumstances, as well as the ones i mentioned. So the user can say sudokutrainer.pl in his terminal and the app should launch.

Best regards, Karl

«The Crux of the Biscuit is the Apostrophe»

Comment on Re^3: How start an application on Linux Select or Download Code

Replies are listed 'Best First'.
Re^4: How start an application on Linux by DrHyde (Prior) on Jan 21, 2014 at 11:14 UTC
Forcing your code to install in particular directories is a Very Bad Idea Indeed. Do not see the "filesystem hierarchy standard". It is Linux-specific, but in any case it is unnecessary. Just rely on perl (via Module::Build or ExtUtils::MakeMaker) to know where to install it.	[reply]
Re^5: How start an application on Linux by karlgoethebier (Abbot) on Jan 21, 2014 at 12:15 UTC
"Forcing your code to install in particular directories is a Very Bad Idea Indeed." Mmh, if i use Module::Build i can force my code to install in particular directories too, isn't it? As far as i understood, i can set `installdirs` to `core`, `site` or `vendor`. So in this case i would end up having a sudoku trainer somewhere in my Perl directory :-[ One might ask so what, but for me this vision is a pain in the ass. On Linux such stuff is traditionally installed in `/usr/local/bin` or `/opt/bin`. IMHO a much better place - and by chance d’accord with Filesystem_Hierarchy_Standard. Best regards, KGB «The Crux of the Biscuit is the Apostrophe»	[reply] [d/l] [select]
Re^6: How start an application on Linux by DrHyde (Prior) on Jan 22, 2014 at 11:56 UTC
Your opinion is of no consequence. What matters is the opinion of the user. If you don't try to tell it where to install, then under normal circumstances (ie, if the user is using a perl that is in his path) then it will install in the path, probably in /usr/local/bin or /usr/bin. Which is what the user wants. Under other circumstances, such as when the user is using some other build of perl, then your code will not unexpectedly pollute the directories in his path. I don't know whether Module::Build will let you force your code into particular directories. But just because it lets you doesn't mean that you should.	[reply]