Where results make sense

About us   |   Why use us?   |   Reviews   |   PR   |   Contact us

Dependency hell - Wikipedia, the free encyclopedia Dependency hell is a colloquial term for the frustration of many users who have installed Linux software packages which have dependencies on specific versions of other packages. Because different pieces of software have different dependencies (the most common being different compiler versions), this often leads to a conflict between the software that is required and the software that is installed. Though the concept of dependency hell has been very common since the rise of package managers, it's actually about as old as Unix itself. en.wikipedia.org /wiki/Dependency_hell   (574 words)

DLL hell - Wikipedia, the free encyclopedia DLL hell is an example of an anti-pattern — that is, a bad programming practice, which should be avoided in well-written software. DLL hell as described above was a very common phenomenon on early releases of Microsoft Windows systems, as they had limited facilities for managing system files and libraries (and existing programs often disregarded the facilities that did exist). A modern example of dependency hell on Microsoft Windows, Linux, and Mac OS X is the Gecko Runtime Engine or GRE used by Mozilla projects. en.wikipedia.org /wiki/DLL_hell   (965 words)

RPM Hell If package A depends on package B and package B depends on C, when you try to install A, it only tells you about the dependency on B. has a low-grain dependency version mechanism. Because to be able to resolve dependency trees, you have to have access to all of the packages in the tree. Dependencies can be easily described with a flexible dependency language, allowing for version ranges, excludes, and includes. www.germane-software.com /~ser/Files/Essays/RPM_Hell.html   (2468 words)

LSB and "Dependency Hell": the Buck Stops Here - OSNews.com What follows in the article is an analysis of the "dependency hell" problem in Linux and the issues surrounding software installation. These projects are attempts to solve some of the issues of "dependency hell" which think "outside of the box" of the conventions already established in the Linux community. Being as it is that most free software makes liberal usage of existing libraries (code re-usage) the potential for "dependency hell" is given. www.osnews.com /story.php?news_id=7922   (773 words)

LWN: Is RPM Doomed? (DistroWatch) While this does mean that I am dependant on the Mandrake community (both commercial and user) for packaging of things that I am interested in, I have found that Mandrake packages are frequently available for even the most obscure packages, if I care to just search hard enough. You seem to be thinking "Dependency hell would still exist in Debian if people tried to install third-party packages." My point of view is "Why would I ever need any third-party packages?" Debian already ships over 10000 binary packages (granted, a lot less than that if you are counting source tarballs). Dependency hell could theoretically affect Debian, but the huge number of native packages that render it a moot point are a feature, not a bug. lwn.net /Articles/24488   (4577 words)

OSDir.com   (Site not responding. Last check: 2007-10-13) Date: Aug 06, 2004 - 10:30 AM "What follows in the article is an analysis of the "dependency hell" problem in Linux and the issues surrounding software installation. Dependency hell occurs when an application requires a multitude of tightly interdependent libraries and those versions expected by the application conflict with previously installed software on the system or when other applications require the same libraries but with different version numbers. This is how the "users" experience dependency hell. osdir.com /PrintArticle1408.phtml   (135 words)

Handling RPM "dependency hell"   (Site not responding. Last check: 2007-10-13) An easy way to install RPMs along with associated dependencies is to use yum (Yellow dog Updater, Modified) or apt for RPM. Of the two products, I would recommend using yum, as it has a smaller code base than apt for RPM, it is written in python (similar to Red Hat's anaconda installer), and it makes upgrading to new Red Hat releases relatively easy (apt for RPM has a dist-upgrade feature, but I have never tried it). However, if you are installing an RPM from another source, you may have to manually determine which packages satisfy dependencies. www.brandonhutchinson.com /Handling_RPM_dependency_hell.html   (407 words)

Re: dependency hell   (Site not responding. Last check: 2007-10-13) The poster then resolved the dependency by installing a second version, not upgrading the existing version. Dependency failures can exist for three reasons: 1) the package isn't installed 2) the package is installed but it's not at a minimum version level 3) the package is installed by it has to be the *exact* version. 3 is a bitch some you may break other packages (package A requires exactly dependency version 1 and package B requires exactly dependency version 2 so you're forced to chose if you want run package A or B but can't run both). info.ccone.at /INFO/Mail-Archives/redhat/Mar-2002/msg01903.html   (275 words)

Linux.com | An apt-get primer Besides the convenience, an advantage of apt-get is that it reduces the chances of falling into dependency hell, that limbo where software installation fails for lack of another piece of software, whose installation fails for lack of another piece of software, and so on. Depending on which Debian-based distribution you are using, repositories are either entered automatically or selected by you during installation. The more libraries included among the dependencies, and the more widespread their use, the greater the chance that your efforts will break your system. applications.linux.com /applications/04/12/03/177243.shtml?tid=47&tid=49&tid=106&tid=126   (2544 words)

NewsForge | Deficiencies in resolving dependencies limit Linux's appeal   (Site not responding. Last check: 2007-10-13) Dependencies are set by the package maintainer, and these are wrong (as it sometimes happens). They should include their own dependencies, and have code for resolving them in a proper fashion, even if it means installing it's own GNOME libraries in it's own directory and modifying the rpath of the executables. Hell, maybe it's possible that an independent group of people will be making emulations DLL's to interface old library methods to new ones in order to fix the issue having different programs using different versions of a library. www.newsforge.com /software/03/10/16/2035254.shtml?tid=130&tid=82&tid=89   (6893 words)

EclipsePlugins : details for the Savant Dependencies Eclipse plugin (Code mngt) Add in the fact that external dependencies may in turn have their own dependencies that must be included and the number of files in the 'lib' directory can grow unwieldy quite quickly. In addition to this, storing dependencies within a project directory requires them to be stored along with the project when using version control. It quickly reaches a state known as "Dependency Hell", in which developers spend a disproportionate amount of time coping with dependencies. eclipse-plugins.2y.net /eclipse/plugin_details.jsp?id=1064   (335 words)

Vikram Goyal's Blog: Dependency hell It may be unpleasant to manage all those dependencies, and I think the JCP should coe with some standard for this area, but it's much better (easier) than writting all the code yourself or coding without those features. I had around 30 libraries in a project, some used directly, some were transitive dependencies (dependencies of dependencies). There are just as many dependencies on build tools and external libraries, but the dependencies sections in the Visual Studio project files are always causing problems. weblogs.java.net /blog/gvix/archive/2006/01/dependency_hell.html   (2509 words)

[pclinuxos] Mono fun....with rpm's   (Site not responding. Last check: 2007-10-13) That's what is called in jargon the rpm dependency hell. What I suggest for a start is that you put all the rpm you downloaded in one directory, then run from there rpm -Fvh *.rpm look carefully to the error messages you get and try to compensate. No guarantee that this won't open another dependency (if it is called "dependency hell" there must be a reason :-)). www.pclinuxonline.com /pipermail/pclinuxos_pclinuxonline.com/2004-June/002182.html   (289 words)

What the hell is up with mono develop - GameDev.Net Discussion Forums Posted - 12/19/2004 1:32:18 AM I found yum to be great to solve dependency hell, if say you want to install mplayer, by calling yum install mplayer *, it will download and install all dependencies for you (which for the mplayer example, are a lot!)... Dependancy hell as far as i understand (and have experianced) is when something has a dependancy that has multiple dependancies which also have dependanices and so on in a seemingly infinate daisy chain of missing files. As soon as the DX SDK is done dowloading on my father in laws slow net connection ill boot up mono and report on the crash messages... www.gamedev.net /community/forums/topic.asp?topic_id=289313&whichpage=1&   (918 words)

FedoraForum.org - install apt = dependency hell Yes, you are not alone, severe dependency problems are like a third hand to me as I have been playing with YUM and such for the last couple of days. I installed an older version of K3b (for redhat 9)....no dependency problems with it...I then did yum update again which found the new version of k3b and all the dependencies that it required.... I am not able to use apt-get anymore, the list of failed dependencies (according to apt, the system works fine, I guess) is so long it is not displayed entirely in my shell. forums.fedoraforum.org /printthread.php?t=189   (709 words)

Re: How to clean up apt-get I have had an order of magnitude worse dependency hell with debian than any redhat distro. Compounded with the fact that on different platforms the debian packages may or may not be stable (sparc support for unstable was spotty for example). Dependency hell is definitely not a redhat phenomena. www.mail-archive.com /plug@plug.org/msg03810.html   (646 words)

CATHOLIC ENCYCLOPEDIA: Knights of Malta Before the Crusades, the Italian hospital languished, sustained solely by alms gathered in Italy; but Gerard profited by the presence of the crusaders, and by the gratitude felt for his hospitality, to acquire territory and revenues not only in the new Kingdom of Jerusalem, but in Europe -- in Sicily, Italy, and Provence. They dispersed to their commanderies and begged Charles V to grant them the island of Malta, which was a dependency of his kingdom of Sicily, and this sovereignty was granted them in 1530, under the suzerainty of the kings of Spain. It will be readily understood that the habit of living in the midst of these scenes of violence and brutality exercised a bad influence on the morals of the knights of the order. www.newadvent.org /cathen/07477a.htm   (3203 words)

LinuxLinks News: An apt-get primer   (Site not responding. Last check: 2007-10-13) hell, that limbo where software installation fails for lack of another piece of software, whose installation fails for lack of another piece of software, and so on. If you know how Debian's archive system works, and how to choose the sources that apt-get uses, and use a few precautions in your upgrades, then the chances are that dependency problems will never bedevil you. Should you descend into dependency hell anyway, apt-get offers useful tools for climbing out of it. www.linuxlinks.com /portal/news/article.php?story=20041209234100500&mode=print   (177 words)

Using APT in RedHat Linux   (Site not responding. Last check: 2007-10-13) You cannot install a package that depends on other packages without installing them also, and you cannot deinstall software that other packages depend on. An integral part of package management is to keep track of these dependencies and take care they are not broken, which may render parts of or the entire system unusable. It will automatically check for dependencies when a (de-)installtion request is issued, and offer to download and install any packages that are required. mgu.mtnsub.org /computers/apt-for-linux.html   (420 words)

Dependency hell - a GNU/Linux specific problem I have to agree that "dependency hell" is the aspect I hate the most. I would like to see a mix of the following qualities: easy dependency checks and full upgrades throughout the whole system, like Debian; the capacity to install different versions, like on FreeBSD and Windows box, while keeping the stability of FreeBSD; and a "roll back" feature in case something goes awry, like Windows ME has. "Dependency hell" won't be solved by an O'Reilly book...it'll only be solved if people are willing to face this problem, that is *very* pronounced on GNU/Linux as opposed to other systems. www.oreillynet.com /cs/user/view/cs_msg/25030   (251 words)

ipedia.com: Dependency Article   (Site not responding. Last check: 2007-10-13) In project management, a dependency is a link amongst a project 's terminal elements. There are four kinds of dependencies with respect to ordering terminal elements : Finish to start A FS B = B doesn... The critical chain method necessitates taking into account resource constaint-derived dependencies as well. www.ipedia.com /dependency.html   (424 words)

No dependency hell 1 KDE-Look.org Rpm and Deb packages cannot ignore version dependencies.Never.That is what made me mad when using debian or fedora.You need to have package version 1.25,but you have package version 1.24 and that is why you cannot install a simple small app that hardly uses the package. Dependencies cannot be ignored with apt,so you have to google for the damn package and this makes me mad,because you dont have a choice.You need to fetch 100mb of useless data to upgrade 0.89 to 0.90 and that all just to get a small package (1mb)installed. The dependency hell is still there, but since it's a lean distro to start wtih, the hell isn't quite so bad as your typical bloated distro. www.kde-look.org /content/show.php?content=34508   (624 words)

Dependency hell is an outdated annoyance.. Urpmi works much like apt-get for Debian, and figures out dependencies automatically, all you have to do is add sources. Even then, some programs might not be fully supported as to all dependencies, although matters are improved. So compiling from source is sometimes the only way, and that requires some research to make sure all dependencies are met...since the library problem doesn't go away, unless you can find a statically compiled binary somewhere. www.oreillynet.com /cs/user/view/cs_msg/24190   (279 words)

RPMs Shortcomings   (Site not responding. Last check: 2007-10-13) Often times these packages will not even be available for your own distribution, and you will be left with the only options of either a) building your own custom RPM for that package or b) building the whole thing from source. Now, this "dependency hell" is really only a problem if you stray from what your distribution supplies for you... Thus, dependency hell is a very real problem for Linux users and administrators. cispom.boisestate.edu /cis121emaxson/rpmshortcomings.htm   (293 words)

NewsForge | Why I do upgrade my Linux systems frequently What he is really talking about is the proverbial RPM Hell and the not-so-good fragmentation of RPM-based distributions. RPM hell is mostly caused by the fact that there is no natural "upstream" authority like their is with Debian. One reference to "rpm hell" made the point; repeated references to RPM this way sound suspiciously like flame-bait and add nothing to the content of the article. os.newsforge.com /os/05/01/11/0129210.shtml   (4849 words)

LWN: An apt-get primer (NewsForge) When you specify a dependency in a package you don't have to specify a specific version. their making it that if you want say kde, all dependencies will be resolved by downloading it as a 'component' in which all needed packages are downloaded. All these issues would affect dependent packages, and is what people usually talk about RPM dependency hell. lwn.net /Articles/114948   (902 words)

Try your search on: Qwika (all wikis)

About us   |   Why use us?   |   Reviews   |   Press   |   Contact us   Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.