I spent a number of hours at one of the local SF clubs turning a desktop into a dual-boot (if they ever need that for anything) CentOS 6.4 system, then trying to install Evergreen, an oss library package. Can you say, "dependency hell"? I suspect they wrote it on Ubuntu (this is client/server software, dunno why they'd do that). At any rate, I yum installed the postgresql 9.x package that pgsql has on their official site, and that installed with no problems at all. Then evergreen. Which wouldn't build, because libmemcache was too old. I tried to build a newer package, after d/l one from the memcache official site. And *that* wouldn't build, because it wanted something that libevent-devel for CentOS 6.4 didn't provide. I've got two possible routes, here: a) I can try to build an older, deprecated version of Evergreen, or I can try to build a newer libevent and stuff - some of which, IIRC, kde wants. Opinions? Suggestions? And if anyone's worked with evergreen, PLEASE TALK TO ME!!! mark
m.roth at 5-cent.us wrote:> I spent a number of hours at one of the local SF clubs turning a desktop > into a dual-boot (if they ever need that for anything) CentOS 6.4 system, > then trying to install Evergreen, an oss library package. > > Can you say, "dependency hell"?Yes, I know what you mean. A couple years ago I was interested in getting Evergreen packaged for centos. Some parts were rather easy to create an rpm file for, but not others. For me the killer was a perl module that required another perl module. And the second module required the first. I tried creating a single rpm for both, but that didn't work. At the time the developers were busy enough with other problems that they weren't able to assist me. My only suggestion would be to try to install everything (in- tead of packaging everything) and use cpan modules liberally (something I had tried to avoid). c
On Mon, 16 Sep 2013, m.roth at 5-cent.us wrote:> Can you say, "dependency hell"? > > I suspect they wrote it on Ubuntu (this is client/server software, dunno > why they'd do that). At any rate, I yum installed the postgresql 9.xI don't think it is appropriate to be derogatory to other distros. Before yum there was 'dependency hell'. However, bear in mind apt-get is a superior package manager to yum... not my opinion but the opinion of many. james
On Mon, Sep 16, 2013 at 11:03 AM, <m.roth at 5-cent.us> wrote:> I've got two possible routes, here: a) I can try to build an older, > deprecated version of Evergreen, or I can try to build a newer libevent > and stuff - some of which, IIRC, kde wants. > > Opinions? Suggestions? And if anyone's worked with evergreen, PLEASE TALK > TO ME!!!I haven't worked on Evergreen, but lately I've found need to build some specific packages that were developed on Debian or Ubuntu based distros. My approach has been to create a separate /opt/foreign mount and then rebuild what libraries I could and place them there. It worked, but I wouldn't want to do it for anything big. If you have a build environment on Ubuntu, I suppose another option would be to statically link everything.
Maybe Matching Threads
- A question about 7
- Conflicts updating packages, hot to get ride of them without mess up all my OS?
- RPMforge for RHEL4: libevent dependency problem
- Broken upgrade to memcached
- Error when compiling tinc 1.1pre3 - configure: error: "curses header files not found."