r-darwish / topgrade Goto Github PK

View Code? Open in Web Editor NEW

3.4K 37.0 161.0 3.01 MB

Upgrade everything

License: GNU General Public License v3.0

Rust 98.65% Emacs Lisp 0.18% Roff 0.79% KakouneScript 0.04% Vim Script 0.35%

rust package-manager automation

topgrade's People

Contributors

Stargazers

Watchers

Forkers

aidanharris byron tversteeg frobware claui mojitmj rayleyva jasikpark nhellwig jcgruenhage bbigras christopherjmedlin kellenff clatour atroche fsquillace ericmarkmartin kornelski idanski eltonlika choman witti br1ght0ne saschpe keruspe mkroman difabion jedahan nginfo9 234d hugoh mdboom heroickatora levbishop woohgit stunkymonkey liaden dillonmenefee fxcebx severinkaderli davemachado askagirl mhaessig ajaxbits asonix linux4life531 migudent marty-oehme n0nz aheritier daocalendar imntreal lenaschoenburg ruonli andveg38 deppiedave64 chhe rajivchirania bashofmann openjck aehmlo sinhasantos c0ding lhaeger ro9ueadmin divinegod emilienmottet yamaton msmafra panticz rmgiroux sparkenstein fallenwarrior2k niheaven terkwood slippycheeze privyack confusedsky kokakiwi wbthomason alexanderwillner mcofficer mortenscheel cclauss akeshihiro alanlima jimsforks pianomanx roryo interlunar jimman2003 alok marcosnils komori pierolenzo krazylegz orbital-transfer-survey m-hauck usmanatmojoo ermshiperete

topgrade's Issues

Vim update should also update the plugin manager itself

For example, for vim-plug in addition to running PlugUpdate topgrade should also run PlugUpgrade. I don't know the equivalent for the other managers.

Show summary of failed upgrades at the end

init.el is looked at the wrong location in Windows

topgrade ignores `--help` flag

$ topgrade --help                                                                                                                                                         
                                                                                                                                                                                                                   
―― System update ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――                                                                                                                                  
:: Synchronizing package databases...                                                                                                                                                                              
 core is up to date                                                                                                                                                                                                
 extra                                                                                               1640.0 KiB   430K/s 00:04 [#############################################################################] 100%
 community                                                                                              4.4 MiB   348K/s 00:13 [#############################################################################] 100%
:: Searching databases for updates...                                                                                                                                                                              
:: Searching AUR for updates...                                                                                                                                                                                    
:: Querying AUR...                                                                                                                                                                                                 
:: 24 Packages to upgrade.                                                                                                                                                                                         
24  core/cryptsetup          2.0.3-1    -> 2.0.3-2                                                                                                                                                                 
23  core/iproute2            4.16.0-1   -> 4.17.0-1                                                                                                                                                                
22  core/json-c              0.13-1     -> 0.13.1-1                                                                                                                                                                
21  core/libsystemd          238.133-1  -> 238.133-2                                                                                                                                                               
20  core/systemd             238.133-1  -> 238.133-2                                                                                                                                                               
19  core/systemd-sysvcompat  238.133-1  -> 238.133-2                                                                                                                                                               
18  extra/bind-tools         9.13.0-1   -> 9.13.0-2                                                                                                                                                                
17  extra/bluez              5.50-2     -> 5.50-3                                                                                                                                                                  
16  extra/bluez-libs         5.50-2     -> 5.50-3                                                                                                                                                                  
15  extra/bluez-utils        5.50-2     -> 5.50-3                                                                                                                                                                  
14  extra/flatpak            0.11.8.1-1 -> 0.11.8.2-1                                                                                                                                                              
13  extra/imagemagick        7.0.7.38-1 -> 7.0.7.39-1

Better error handling

Update procedures should be exported to functions that returns Result and fail when the process fails. The main function should not propagate these errors, but instead report them to the console

Use the "directories" create for finding the configuration directory

topgrade should first upgrade itself and relaunch

Windows support?

It would be really nice to be able to run this on Windows.

Suggested package managers:

Chocolatey
MSYS (Pacman)

Check for administrative privileges in Windows

Does not recognize Antergos

Currently trying out Antergos and Topgrade gives "Error detecting current distribution: Unkown Linux Distribution"

HEre is the content of the os-release file:

NAME="Antergos Linux"
VERSION="18.7-ISO-Rolling"
ID="antergos"
ID_LIKE="arch"
PRETTY_NAME="Antergos Linux"
CPE_NAME="cpe:/o:antergosproject:antergos:18.7"
ANSI_COLOR="1;34;40"
HOME_URL="https://antergos.com/"
SUPPORT_URL="https://forum.antergos.com/"
BUG_REPORT_URL="https://github.com/antergos"

Add pre-update commands

Parallalization

We can perform git pulls in parallel, as well as non interactive upgrades such as vim, emacs, etc.

The system upgrade should not run in parallel.

Vim

Neobundle
Plug

Add flag for automatic reboot

Use failure instead of error chain

Windows Update

Invoke NPM only if packages will be installed at the home directory

Allow skip checks option during run

I think topgrade is really neat, however... when I'm installing a lot of package dependencies in rapid succession while trying to figure out what I need to build something else, I wish there were a way to override the topgrade checks if I've just run apt commands in the last few minutes.

Something like "press 'q' to skip upgrade checks"

Also, perhaps an internal config setting like "don't check for upgrades if last run was less than N hours/days ago" -- that might be a good overall solution.

Use match instead of if-let in terminal module

Git doesn't follow symlinks in Windows

sudo should not reference relative paths

It's easier to have sudo reference a relative path, like sudo yum upgrade, but there's basically only two cases where that would work.

sudo is configured to allow ALL as root
sudo is configured to allow a relative path, like just saying yum

While 1 isn't uncommon, 2 should never be done for the sake of security, because anyone could drop any file in ~ and name it to the relative name to satisfy the requirement.

I think that a better approach here would be to have an assumed path on the various distributions for the binaries and have sudo exec from there. It's pretty safe to assume that on Debian, that apt-get will be /usr/bin/apt-get, and if it isn't, I don't know that I'd trust it unless they officially made a move.

As part of supporting different distributions, I think this would be the safest choice.

sudo /usr/sbin/update-usbids
and
sudo /usr/sbin/update-pciids

to pull the latest snapshots for each.

Thanks!

Brew recipe

Homebrew/homebrew-core#31370

Rustup

I'm not sure what to do with Rustup, so I'm opening it up for discussion:

The stable channel - It's safe to update. However, Rust versions don't release often, and when they do, people are usually aware of that, so maybe it's a bit of a waste to try to update something which doesn't update very often?
The nightly channel - This actually updates every night, but has the potential for breaking things. I don't use nightly personally so I'm not sure what's the desired workflow for people who actually use nightly. Do such people update nightly every day, or do they only do that whenever they feel ready?

custom commands
custom git repositories

r-darwish / topgrade Goto Github PK

topgrade's People

Contributors

Stargazers

Watchers

Forkers

topgrade's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs