Issue #3197 has been updated by justin.

tse wrote:
> 4.8 looks good to me. Feel free to re-download and try it out

I am not sure how to describe this exactly, but I'm thinking it would be better 
as an action - upgrade --release for the current release version, 'upgrade 
--bleedingedge' or similar for HEAD.  Kitchen sink scripts that handle 
maintenance are good but they tend to grow and then collapse under their 
weight.  

I may be overthinking this.

----------------------------------------
Bug #3197: DragonFly upgrades
http://bugs.dragonflybsd.org/issues/3197#change-13763

* Author: tse
* Status: New
* Priority: Normal
* Assignee: 
* Category: Feature request
* Target version: 
----------------------------------------
Hiya,

I realize this is quite a simple script, and possibly misses useful features 
(?). Originally posted to @users, but mailing list line-wraping didn't keep the 
script fully intact, so copy/paste/test wouldn't of worked

Also, the response on DragonFly Digest encouraged me re-post it here

I've tested it on new installs of 4.8, 5.2, and 5.4, and with installs 
previously upgraded with `make src-create/src-create-shallow`

It takes this:
------
> cd /usr
> make src-create
> ...
> make buildworld
> make buildkernel
> ...
> make upgrade
------

To this:
------
> /usr/upgrade
Upgrading DragonFly BSD

For more information see:
  `man build`      `man config`
  /usr/src/README  /usr/src/UPDATING
  http://www.dragonflybsd.org/docs/handbook/

It is possible to run this script without root privileges
Usage:  upgrade [configuration]
Configuration is "X86_64_GENERIC"

Latest releases:
  [1]  DragonFly_RELEASE_5_6
  [2]  DragonFly_RELEASE_5_4
  [3]  DragonFly_RELEASE_5_2
  [4]  DragonFly_RELEASE_5_0
  [5]  DragonFly_RELEASE_4_8

Select [1-5]:
------

---Files--------------------------------
upgrade (2.4 KB)


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://bugs.dragonflybsd.org/my/account

Reply via email to