On Sun, 2004-10-10 at 21:17, Alexander Dalloz wrote: > Am Mo, den 11.10.2004 schrieb W. Guy Thomas um 3:41: > > > The web portion of an application should be ubiquitous and not require a > > reconfiguration per site. > > How should it work than? Please think a bit. Should there be one big > repository containing all? All repositories be configured by default? > Both make no sense. Please search the list archive i.e. for discussion > about mixing the different repositories. > One big repository would of course be senseless. My point is that each site should adhere to a structure that makes it the same for each user rather than each user having to change the structure of their yum.conf file per site as in DIRECTORY STRUCTURE. Why would some sites require you to go to .../basearch/yum, and others go straight to .../basearch/os? Again, the *web* portion of an application should be invisible to the user in most cases. Tweaking allowed of course, but for an application like yum that is supposed to be "automatic" it shouldn't require tweaking paths. > > Yum itself could and should require many parameters, but to change the > > option of using $releasever and $basearch and require editing per site > > takes away the power of yum and what it could be. > > Those variables don't have to be changed. > Of course not. That's not the point. The path following those variables *does* however and shouldn't have to be. > http://www.fedoratracker.org/tracker.py?mode=repoSearch > > Makes it maybe easier for you. I feel you have to read a bit and to > understand how yum or up2date or meant to be used. > > > =G > > If you feel better use rpm directly. Much fun then ;) > No thanks. Been there. Done that. About 8 years ago in th pre-2 kernel days. > Alexander > Take care. =G
