Issue #3197 has been updated by tse.
File upgrade added
Make sure user has options when network offline
Bug #3197: DragonFly upgrades
http://bugs.dragonflybsd.org/issues/3197#change-13879
* Author: tse
* Status: New
* Priority: Normal
* Assignee:
*
Issue #3197 has been updated by justin.
tse wrote:
> Feel free to change the wording or anything else; or ask for any changes.
This works well - I imagine 95% of the use cases are going to be "upgrade
within current version" or "move to next release" so I want that to be as
little guesswork
Issue #3197 has been updated by tse.
File upgrade3 added
Hiya,
I think this gives you what you asked for:
Upgrading to HEAD can be equally done with '-r 0' or '-r unstable' or even '-r
master' and '-r 273ce6e304'
Upgrading to the latest release can be done with '-r 1' '-r stable' or even '-r
Issue #3197 has been updated by tse.
Or something like '-r stable' and '-r unstable' would be easy to add
Bug #3197: DragonFly upgrades
http://bugs.dragonflybsd.org/issues/3197#change-13767
* Author: tse
* Status: New
* Priority: Normal
* Assignee:
*
Issue #3197 has been updated by tse.
File upgrade2 added
Yup, lets leave the Makefile
> Let's go even simpler - if a branch isn't named, as either RELEASE, HEAD, or
> (Git commit ID), assume that it's an update of whatever branch is currently
> in place. No menus or choices needed.
For
Issue #3197 has been updated by justin.
tse wrote:
> If people don't pass a [ -r RELEASE ], then the script will give the release
> options to select from
Let's go even simpler - if a branch isn't named, as either RELEASE, HEAD, or
(Git commit ID), assume that it's an update of whatever
Issue #3197 has been updated by tse.
You're right, some people will want HEAD, and seeing @yellowrabbit do a commit
bisect, a one liner upgrade to named commit would also be nice
I wanted to avoid required flags, so people don't have to re-look them up, but
an optional flag like [ -r HEAD |
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
Issue #3197 has been updated by tse.
File upgrade added
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
