Where Did Yum Install Monodevelop?

Home » CentOS » Where Did Yum Install Monodevelop?
CentOS 20 Comments

Hello all, I’m running CentOS 6.4.

Today I tried installing monodevelop and this is the result of the installation:
http://bin.cakephp.org/view/258829139

Now. When I went to my terminal and ran monodevelop… nothing. When I tried to locate the actual executable by running find . -name “*monodevelop*” (kinda overkill, but figured that I’d get this option out of the way), I couldn’t find anything. So, now, I’m scratching my head and wondering what to do next :) . Where did I mess up? Am I not starting monodevelop correctly? If so, how should I start it?

20 thoughts on - Where Did Yum Install Monodevelop?

  • Yves S. Garret wrote:
    scratching

    It may not have done your PATH correctly. Easy answer:
    rpm -ql monodevelop

    which gives you a full path listing of all the files.

    mark

  • Perhaps it isn’t. Your initial post indicates that you have base, epel, extras and updates repositories enabled. I have the same on this computer.

    “yum search monodevelop” tells me “no matches found.”

    So where did you find the monodevelop rpm that you think you installed?

  • Yves S. Garret wrote:

    Right. rpm -qa | grep -i monodevelop

    If that gives you nothing, try yum list monodevelop.

    And please don’t top post.

    mark

  • That’s an unvetted repo that is mentioned in that article, and from the looks of it is providing unsigned packages? Bleah.

    John

  • I also don’t see any place where they are providing source rpms in their repo, though I didn’t spend a whole lot of time searching. Therefore, it would be difficult/impossible to check their spec file and see what that package actually does and where it wants to put stuff.

  • Yves S. Garret wrote:

    And there’s your answer – it doesn’t like the repo. Also, you really should pay attention to the other folks’ comments, questioning the security of what you want to install.

    mark

  • I just deleted that repo.

    And yes, I knew I was taking a risk. To be honest, I wasn’t sure what to do next after hitting my head against the wall so much, hence such drastic measure.

  • You may be asking the wrong question.

    What were/are you trying to accomplish (outside of just “install monodevelop”, which I had never heard of before today)?

    Is your objective simply to install a good programmer’s editor/IDE? If so, for what programming language? For example, perhaps something like vi, emacs, geany or eclipse would meet your needs, depending on what your needs actually are.

    Is your objective to do mono API programming using something like C#? If so, is there any particular reason why you want to use that instead of some other programming language?

    If you tell us what you’re really trying to do, perhaps we can give you a recommendation for what your best course of action would be.

  • I would like to do some coding in C#. The problem that I was encountering is if your code is split up over several files (you have a factory class and a widget class and then, just for fun, a bird class) is getting all of the files to include correctly and link correctly. I’ve tried monodevelop on my Mac, it did the trick and I wanted to do the same on my CentOS machine.

  • It’s entirely possible that I’m missing something, but how does that tell me what pre- and post-install steps the rpm does, or what patches are applied to the binaries? All I get is a list of files and directories. I don’t think it’s possible to extract a spec file from a binary rpm. Or is it?

  • As such it is not possible to retrieve the complete spec. The actions can be viewed however with the — script option to rpm, eg:
    rpm -q –scripts binutils

    I do not see how one can see what patches are installed.

    The problem the OP has comes from the fact that the rpm is not signed, so it must be installed with the –nogpgcheck option to yum. Without the option IIRC yum complains about the missing signature and does not install the package.

  • You could have let it go at the first line: The problem is indeed that the rpms are not signed. –nogpgcheck is not a viable option on a server you care about unless you are 1000000% sure (ie. audited everything yourself and/or built the rpm yourself) that things are germane.

    John

  • Indeed, installing an RPM from an unknown source, even if it is signed
    (with a key from the same source) is taking a big risk. I assumed that the OP understood that…..

  • Am 20.05.2013 19:06, schrieb Yves S. Garret:

    Of course it isn’t. Your original result:

    clearly shows yum aborting with an error:

    and not installing anything.

    HTH
    T.

LEAVE A COMMENT