Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm using Cygwin 2.769. I used setup.exe to upgrade Perl to version 5.14.1-2, which works fine. But now whenever I open setup.exe to upgrade/install some other package, it by default wants to downgrade Perl back to 5.10.1-5. If I don't remember to manually cycle that box over to my current version each time, Perl gets downgraded without my noticing.
Is this expected behavior, or have I hosed something up? It seems like using the "Curr" setting should not by default downgrade things.
I've had this problem, and it's made package managers almost unbearable. When disparate packages want to rely on different versions of a package that can only install in one version at a time, bad things happen.
Don't use the system perl for anything. Install a perl that other packages don't care about.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I am a massive fan of Homebrew and have taken to using it to manage all my applications. One very useful feature is brew switch which enables switching between different versions of Ansible. Something which I require to compile some of my websites running older software.
However, I have noticed that whenever I wish to run brew cleanup, it deletes all old versions even version 2.3.2.0 of Ansible which I still require alongside the most current version.
After sifting through numerous forums and sites I have been unable to find a solution which allows me to keep this old version of Ansible and the most current when using the brew cleanup command other than deleting everything manually.
Does anyone have a workaround or solution, I thought brew pin may be a possibility, but this seems to only work with the version currently linked.
I don't see a clean built-in way with brew cleanup to do this, but a workaround: since brew cleanup optionally takes a list of formulae to clean up, we can make such a list that contains everything but Ansible.
This is how I can get that list:
brew list | grep -v ansible
And this is how I can call cleanup to ignore Ansible:
brew cleanup $(brew list | grep -v ansible)
Maybe I want that as an alias somewhere, like bca for "brew cleanup (but not) ansible":
alias bca='brew cleanup $(brew list | grep -v ansible)'
and add that line to my ~/.bashrc.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
I need to execute a program in my system using the perl.exe from a network path.what change should I have to change in the interpreter line to execute that..?
There's a fair chance (given that the question gives us no clues to help us answer it) that the perl.exe is just a wrapper for perl.dll, so if the perl.exe isn't on the path (and it won't be if its on a network share) then the exe will fail to run.
The answer is almost certainly to copy the required files locally and run them there. I recommend Strawberry Perl for Windows, as its just a directory copy to get it installed.
Invoking using a remote exe may not work due to the exe's own dependencies. Consider packaging your perl script as an exe using http://search.cpan.org/dist/PAR-Packer/
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I used maven to download mahout and hadoop recently. Because I could not seem to do that without using sudo mvn commands, eclipse could not seem to be able to use anything I had downloaded (there were lots of errors like parents of things like POM.xml being permission denied etc.) and more recently than that I was trying out mahout (with local jars downloaded directly from one of apache's mirrors, not from maven) and although I could run the class the first time, I couldn't do it again because my eclipse instance could not overwrite the file I had already written.
These are just examples of times I feel it would have been good to be running eclipse as superuser by doing
sudo eclipse
Instead of just launching it normally. The only problem I can think of is that as root eclipse suggests you use the root/workspace, but is it ok to just tell it to use yourusername/workspace?
In general- no. It's tempting, but not very good practice to do all of your development as the superuser. If you're running Eclipse as root, then you're also launching Java processes as root when you run your software. (You could change your Java run settings to sudo back to a regular user before running, but I wouldn't recommend that as a solution).
In addition to being a security risk, you are also making it difficult to track down bugs if you want to distribute the software to others to run as non-root (e.g. doing root only things like reading a protected file or using a well known port might work for you, but not for the average user).
I recommend finding the files that are causing issues and doing chmod o+r on them.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Is there any difference between rpm and yum? I know the recent system prefer yum, but want to know if there is need for rpm also.
to expand on the Udo's answer, there is the program, "rpm", which manipulates specifically the packages it is asked to manipulate, and there is "yum", which is a more intelligent management system that can find dependencies and download .rpm files even if they're not in the system.
with the "rpm" command, you need to know the exact location of the .rpm package, but with "yum", you just need to know the name of it, and as long as it's available through your repositories list, it will be installed along with its dependencies
Yum is a package manager and rpms are the actual packages.
With yum you can add or remove software. The software itself comes within a rpm.
The package manager allows you to install the software from hosted repositories and it will usually install dependencies as well.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Since May 14th the current version of Perl is 5.14. In Ubuntu repository the current version of Perl is 5.10 which is no longer supported. So Im trying to manually upgrading Perl.
What is the recommended way to upgrade perl 5.10 to perl 5.14 in Ubuntu?
I found the perlbrew tool, but it seems to install just in the users home.
Perlbrew docs says that you can change your $HOME dir to something else:
The directory ~/perl5/perlbrew will contain all install perl
executables, libraries, documentations, lib, site_libs. If you need to
install perlbrew, and the perls it brews, into somewhere else because,
say, your HOME has limited quota, you can do that by setting a
PERLBREW_ROOT environment variable before running the installer:
export PERLBREW_ROOT=/opt/perlbrew curl -L
http://xrl.us/perlbrewinstall | bash
download, configure, compile ....