Re: broken VIM update on FC3??

From: Paul Howarth (paul_at_city-fan.org)
Date: 08/12/05

  • Next message: Todd Nine: "Re: Sending hostname with DHCP"
    Date: Fri, 12 Aug 2005 16:28:56 +0100
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    Tony Nelson wrote:
    > At 8:14 AM +0100 8/12/05, Paul Howarth wrote:
    >
    >>On Thu, 2005-08-11 at 17:29 -0400, Tony Nelson wrote:
    >
    > ...
    >
    >>>But why was [vimrc.rpmnew] created anyway? I'd have thought that there
    >>>would be at least minimal merge logic which would not make .rpmnew files
    >>>when the file would be identical with the original.
    >>
    >>My understanding of the logic for configuration files in package updates
    >>is:
    >>
    >>if old-rpm-config-file is identical to new-rpm-config-file
    >>then
    >> leave the installed-config-file unchanged
    >>elsif installed-config-file is identical to old-rpm-config-file
    >>then
    >> install new-rpm-config-file
    >>elsif config file marked (noreplace) in rpm package
    >>then
    >> install new-rpm-config-file as new-rpm-config-file.rpmnew
    >>else
    >> rename installed-config-file installed-config-file.rpmsave
    >> install new-rpm-config-file
    >>endif
    >>
    >>Given that vimrc has not changed over many releases, one might expect
    >>that vimrc.rpmnew files shouldn't get created, but they always do. I
    >>believe that the reason for this is that /etc/vimrc is included in both
    >>the vim-minimal and vim-common; there's no conflict between these two
    >>packages because the vimrc file is the same in both packages, but rpm
    >>seems to create the .rpmnew file anyway.
    >
    >
    > Thanks, Paul. I see the (noreplace) in the spec file. I don't think I
    > quite understand subpackages yet.

    All a subpackage is is a separate binary package built from the same
    source/spec at the same time. So for instance there's zlib and
    zlib-devel, both built from the zlib src.rpm. The -devel package
    contains various things that not all users of zlib will need, so it's
    broken out into a subpackage so that those bits don't need to be
    installed unless you actually need them. As far as RPM itself is
    concerned, once the subpackages are built, they're entirely separate
    packages with no relationship between them (though it's usually the case
    that the packager will specify in the spec file that one depends on the
    other, e.g. you can only install zlib-devel if you have zlib installed).

    Paul.

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Todd Nine: "Re: Sending hostname with DHCP"

    Relevant Pages

    • [PATCH 1/2] kbuil: add deb-pkg target
      ... # To prepare kbuild for more kernel packaging formats move all packaging ... # In top-level Makefile introduce generic support for all package ... Included the old rpm target for backward ... # and builddeb scripts. ...
      (Linux-Kernel)
    • Re: Conventions for NFS sharing of binaries
      ... Do you have distro & local packages with same name? ... mount it r/w on your "master installation machine" (with RPM management). ... If you replace a package with a different one with the same name, hmm, you ...
      (comp.os.linux.misc)
    • Re: ./configure command
      ... The package is not available. ... machines which don't even have an OS at all, let alone RPM, ... There is not a "the tool to package and install on Fedora". ... If he wants to avoid trouble, ...
      (Fedora)
    • Re: Backing up whole system
      ... Amanda is packaged by Fedora and if Gene feels that the packages are ... fedora's rpm is/was incapable of handling the nuances of using only enough ... When an rpm package can build a complete user from scratch, ... Do you really believe that rpm can install every package under the sun, ...
      (Fedora)
    • Re: Redhat to Freebsd
      ... >>researching security updates or in performing kernel or package updates. ... >>I assume it is only the Redhat distro that has the ease of RPM installation? ... So you can build from sources with ports, or install binaries ...
      (comp.unix.bsd.freebsd.misc)