Boutique to have responsibility across upgrades/source changes.

[flexiondotorg]

Originally reported by: Luke Horwell (Bitbucket: lah7, GitHub: lah7)

---

A possible problem for users of 15.10 to 16.04 who installed their software via the Boutique is that PPAs/sources are disabled across upgrades.

Also, in the rare event old pre-installation data in the index had changed (eg. PPA deprecated/changed and the user should switch to the new one for that app's updates), Welcome cannot do that unless the user manually re-installs.

I think the Boutique should have a responsibility to keep sources updated.

Implementations would be needed for:

• Tracking packages installed via Welcome and checking old records.

• Detecting when a distro codename has changed (wily → xenial) and:

• • Removing the old source.
• • Adding the new source for the new codename. (If needed)

• Kindly informing the user about changes and seeking permission to make changes.

---

• Bitbucket: https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issue/10

[flexiondotorg]

Original comment by Martin Wimpress (Bitbucket: flexiondotorg, GitHub: flexiondotorg):

---

Perhaps adding the ability for Welcome to detect if the appropriate sources file is present in /etc/apt/sources.list.d/, and if not, presents just an Upgrade button would be sufficient because we know applications.json know what releases are compatible.