Mailinglist Archive: opensuse (2974 mails)

["Bryan Liles" <BLiles@xxxxxxxxxxxxxxx>]

   * how to create an RPM that will install into a SuSE configuration
without 
   breaking the current dependencies.  e.g., I am trying to build the
current 
   OpenSSH from tarball, and would like to apply it as an upgrade to the
latest     
   SuSE rpm.

Someone does need to write a book on this subject.  The best thing that I
can
tell you is to look at the src rpms that come with suse.  They will give you
a great deal of clue about the "SuSE way of things"

   * What is the overall architecture of the system.  In this case much of
the 
   information is in the current set of books it is just not organized as a 
   study guide.  

I think (yeah I'm not sure) SuSE follows the LHS.  The only weirdness I've
seen
(weird in my eyes) is the the suseconfig and /etc/rc.config stuff.  But
after
working with it for a few weeks, it has started to make a lot of sense

   * What is the SuSE prescription for modifying system configuration via
RPM 
   scripts.

Again, I would advise you to look at suse packages src rpms

   * How to use the gnu tools such as gcc, make, autoconfig, and etc.

Actually this would go beyond suse in my eyes...  These tools aren't
operating system 
or architecture dependant from the client side

   * How to check the signatures on tarballs that I download.

You could use the md5sum program (/usr/bin/md5sum)  And rpm has has the
--checksig 
options for signed rpms

   * How to sign tarballs

You really don't sign tarballs.  You could generate a md5sub and keep in the
directory
of your tarball if anyone cares to download it and compare.


***********************************************************
The information transmitted in this email is intended only for
the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material.  Any review, 
retransmission, dissemination or other use of, or taking of
any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.
If you received this email in error, please contact the
sender and permanently delete the email from any computer.