Generally speaking, log files are not part of the package. If I remove
apache for instance, it will leave its log files behind. If I upgrade
apache, it will no overwrite the existing log files. When you look into
the apache spec file you will see the log directory in the package file
list, but not the logs themselves. Since there are unknown files in
that directory when the RPM is removed, rpm leaves the directory
behind. In an upgrade the directory is there in the old and new
packages, the files are untouched.
Woody
On Mon, 2002-09-02 at 01:07, James Sparenberg wrote:
> All,
>
> When creating a new rpm of a product that is an update to a previous
> one I need to ensure that previous log files don't get overwritten with
> new versions and blank them out. Many of the Mandrake RPMS are able to
> handle things like this elegantly by saving new files as rpmnew. How is
> this handled in rpm?
>
> Second is there any way to build an rpm with an either/or dependency?
> I've run into problems with a cross distro situation. One names an rpm
> with a - another with an _ Would this be handled in the program itself
> or can an rpm be created with a dependency as a boolean or rather than
> an and.
>
>
> James
>
>
>
>
>
> ----
>
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com
--
Woody
---------------------------------------------------------------
Gatewood Green Network/System Administrator
Email: [EMAIL PROTECTED]
http://www.linif.org/ Linux in Idaho Falls Linux User Group
---------------------------------------------------------------
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
