This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_critter.penguinmonster.com-4416-1048517387-0001-2 Content-Type: multipart/alternative; boundary="=-KwEplzMFGxwCRAqW7sjQ" --=-KwEplzMFGxwCRAqW7sjQ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-03-24 at 08:30, Brad N Bendily wrote: > >=20 > > I don't think I understand what you mean by "circular" dependencies. If > > two rpms depend on each other, install both at once.=20 >=20 > "Install both at once" ? This isn't always reasonable, if you have two rp= m > packages and one depends on the other to be able to install how do you=20 > install both at once? Even if you use rpm -Uvh * one gets installed befor= e > the other. In this case --nodeps lets you install each and the program=20 > will have it's dependencies once both packages are installed.=20 >=20 > This was the main problem I was running in to with the KDE rpms. Like I=20 > said though, everything is running great so --nodeps wasn't detrimental i= n > my case. >=20 >=20 When you specify multiple packages at once, rpm knows what each package is providing and uses all those to determine what will be met. For instance, if foo.rpm requires bar, and bar.rpm requires foo. doing "rpm -ivh foo.rpm bar.rpm" will install both without complaining about missing dependencies.=20 > >=20 > > I, for one, can say that I do know what I'm doing, and I _never_ break > > dependencies on a production machine. I just don't see the point of not > > solving them. >=20 > As for a "production machine" I prefer to compile everything from source. > I didn't compile kde from source because it's a hog to compile. Almost > every other software I use, unless source is not offered, I will compile=20 > it to know that I have more control over the installation. And plus i'm > an uber geek and I just want to do stuff the hard way!=20 >=20 Eww. I avoid source-only installations at all cost. I like making a system as reproduceable and maintainable as possible. Recompiling for every security fix is a nightmare. If I absolutely need some custom configurations that aren't provided by the originating RPM, then I'll modify the SRPM and roll my own. I've even created my own yum repository (http://www.linux.duke.edu/projects/yum/) to keep track of custom packages and be able to update them with upstream providers.=20 -Tim --=-KwEplzMFGxwCRAqW7sjQ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8"> <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/1.1.8"> </HEAD> <BODY> On Mon, 2003-03-24 at 08:30, Brad N Bendily wrote: <BLOCKQUOTE TYPE=3DCITE> <PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>>=20 > I don't think I understand what you mean by "circular" depen= dencies. If > two rpms depend on each other, install both at once.=20 "Install both at once" ? This isn't always reasonable, if you hav= e two rpm packages and one depends on the other to be able to install how do you=20 install both at once? Even if you use rpm -Uvh * one gets installed before the other. In this case --nodeps lets you install each and the program=20 will have it's dependencies once both packages are installed.=20 This was the main problem I was running in to with the KDE rpms. Like I=20 said though, everything is running great so --nodeps wasn't detrimental in my case. </I></FONT></PRE> </BLOCKQUOTE> <FONT SIZE=3D"3">When you specify multiple packages at once, rpm knows what= each package is providing and uses all those to determine what will be met= . For instance, if foo.rpm requires bar, and bar.rpm requires foo. doing &q= uot;rpm -ivh foo.rpm bar.rpm" will install both without complaining ab= out missing dependencies. <BR> <BR> <BR> </FONT><BR> <BLOCKQUOTE TYPE=3DCITE> <PRE><FONT COLOR=3D"#737373" SIZE=3D"3"><I>>=20 > I, for one, can say that I do know what I'm doing, and I _never_ break > dependencies on a production machine. I just don't see the point of no= t > solving them. As for a "production machine" I prefer to compile everything from= source. I didn't compile kde from source because it's a hog to compile. Almost every other software I use, unless source is not offered, I will compile=20 it to know that I have more control over the installation. And plus i'm an uber geek and I just want to do stuff the hard way!=20 </I></FONT></PRE> </BLOCKQUOTE> <BR> Eww. I avoid source-only installations at all cost. I like making a system = as reproduceable and maintainable as possible. Recompiling for every securi= ty fix is a nightmare. If I absolutely need some custom configurations that= aren't provided by the originating RPM, then I'll modify the SRPM and roll= my own. I've even created my own yum repository (<A HREF=3D"http://www.lin= ux.duke.edu/projects/yum/">http://www.linux.duke.edu/projects/yum/</A>) to = keep track of custom packages and be able to update them with upstream prov= iders. <BR> <BR> -Tim<BR> <BR> </BODY> </HTML> --=-KwEplzMFGxwCRAqW7sjQ-- --=_critter.penguinmonster.com-4416-1048517387-0001-2 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: 7bit Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+fxkvtfFnsyEoWxsRArNyAKCsEKkaJGOOrIC3yZlUQ1h873TOPwCgsWua u6Oj0VJspnfxaKaTmpGvFd8= =jQky -----END PGP SIGNATURE----- --=_critter.penguinmonster.com-4416-1048517387-0001-2--
