#6432 NORM Never A: Autoinstallation of RPMs

[Zarro Boogs per Child]

#6432: Autoinstallation of RPMs
-------------------------+--------------------------------------------------
   Reporter:  cscott     |       Owner:  cscott        
       Type:  defect     |      Status:  new           
   Priority:  normal     |   Milestone:  Never Assigned
  Component:  distro     |     Version:                
 Resolution:             |    Keywords:                
Next_action:  never set  |    Verified:  0             
  Blockedby:             |    Blocking:                
-------------------------+--------------------------------------------------

Comment(by cscott):

 > What is 'yum localinstall' actually doing for us, that 'rpm -Uvh *.rpm'
 isn't?

 From mail from mikus:

 > Presumably "yum' records what it did in its own log, whereas 'rpm' by
 itself does not affect the yum log.  Also, 'yum' (depending on how it is
 set up?) saves what it installs - one needs 'yum clean' to empty the yum
 cache;  'rpm' (as far as I know) does not cache the data it works with.

 > I'm the one who suggested 'yumdownloader --resolve'.  With packages
 which I expect to continue to be available in (fedora?) repositories I
 will use vanilla 'yum' - it downloads the "rpms" and installs them.  With
 packages that I had to go find, I'll usually want to manually keep a copy
 on my "permanent" SD card.

 > I was faced with the problem that 'yum' did not give me "no-brains"
 access to the "rpms" it fetched.  Thus to me discovering 'yumdownloader'
 was a godsend -- if I want to store a local copy of some "rpm" from an
 appropriate repository, I access that repository with 'yumdownloader
 --resolve' instead of with 'yum'.

 > Once the "rpms" have been downloaded, the question is how to organize
 them, in case the developer does not wish to (re)apply all the "rpms" he
 has stored.  A common Linux way to organize materials is to use
 subdirectories.  By saying to install packages from '*.rpm' I implied that
 the person doing the install was accessing a specific subdirectory (of
 stored "rpms").

 > For myself, I always use 'rpm -Uvh' to install locally stored packages,
 instead of 'yum localinstall'.  (I don't need whatever additional services
 'yum' provides.)  But since all previous text in this ticket had talked
 only about installing with 'yum', I wrote up using 'yum localinstall' -- I
 saw no need to "break new ground" by suggesting *not* using 'yum' to
 perform the not-using-net install.

 cscott says:

 Is there any chance that installing the packages directly using rpm will
 confuse 'yumdownloader --resolve' later?  If not, I'd say let's install
 using rpm.  I'm not sure developers will quickly embrace a solution which
 adds almost 4 minutes to their upgrade process.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6432#comment:18>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system