DragonFly commits List (threaded) for 2008-01
DragonFly BSD
DragonFly commits List (threaded) for 2008-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvs commit: src Makefile.inc1 Makefile_upgrade.inc src/etc Makefile


To: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
From: Sascha Wildner <saw@xxxxxxxxx>
Date: Sun, 13 Jan 2008 21:53:56 +0100

Matthew Dillon wrote:
:Matthew Dillon wrote:
:> Looks good, though I have a question: Why install the file anywhere?
:> Why not have make upgrade simply access the file directly from
:> /usr/src/etc ?
:
:Hmm, the original idea was to ensure that the list of files fits the :most recently installed world (to not accidentally break things if :upgrade is run before installworld).
:
:Not sure if the 'installcheck' target is the best place to install the :file, tho.
:
:Sascha


    The /etc/.release idea was to store the release id of the last
    installworld and have make upgrade check it and bail if it isn't
    the latest release.

    I'd rather release info be stored in the more read-only-like /etc
    then a file list in the read-write /var/db.  /var/db gets messed around
    with by the boot code, it's not a good place to store a semi-static
    file needed for upgrading.

What exactly should be in /etc/.release? Only "1.10" or "1.11" would not be enough IMO.


I'm mostly concerned about people tracking HEAD and harming their systems because they do make upgrade before installworld with a new file list at some time where it removes some sensitive stuff which needs the _really latest_ HEAD installed.

Sascha

--
http://yoyodyne.ath.cx



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]