On 5 Jun 2003, seth vidal wrote: > > > <itemize> > > <item> Either .yumrc or e.g yum -f myyum.conf to replace /etc/yum.conf. > > Right now one has to edit /etc/yum.conf as root to add a repository > > "permanently". This is not desireable, especially if one only wishes to > > graze one of the other public repository to see what they have or to get > > a single package. Remember, every repository on that list is presumed > > to be infinitely trusted as any RPM installed as root from there can > > destroy every system that updates from it literally overnight. > > yum -c yourconf works just fine. > > it's in the man page. Who is that man and why is he (obviously a Complete Idiot(tm)) writing the HOWTO? > what does -u do? > > yum -c takes urls to config files. > > do you mean to specify an arbitrary place to look for files etc? Where > would a non-root user store the metadata that yum needs? Um (being the aforementioned Complete Idiot:-) where does it store them now when yum is invoked from userspace? Does it just run off of the existing header image cache (always) or invoke a privileged retrieval of the headers? Hold on...hmm, guess it just barfs and dies. For obvious reasons, come to think of it. Ok, OK, "never mind". > > <item> "make rpm" as a make target. I'm happy to contribute this as I > > use one routinely. To build a yum repository, as far as I can tell one > > MUST build the yum rpm after customizing /etc/yum.conf and so forth for > > the site. Sure, y'all probably build rpm's in your sleep, but > > documenting the build process for a novice administrator who > > nevertheless wants to get started using yum is even more work than > > building a make target. Although I'm doing it anyway <sigh>. > > make rpm target gives me hives and ultimately is a lousy way to test to > make sure your tarball is correct. > > I do a make dist > then rpmbuild -ta yum-somever.tar.gz > > yum-arch doesn't at ANY TIME need a yum.conf file so a repo doesn't need > any editing of the rpm. No, but setting up a LAN that will get yum from the repo and automaintain does, does it not. What is the (deep) motivation for building the yum RPM if you're just going to install it on a single repository or system and not distribute clients for it? Aside from being public spirited and all of that? In other words, doesn't just about everybody who installs yum as a LAN maintenance tool that DOESN'T run from the default dulug repository need to build an rpm? rgb > > -sv > > > > > -- Robert G. Brown http://www.phy.duke.edu/~rgb/ Duke University Dept. of Physics, Box 90305 Durham, N.C. 27708-0305 Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
