BUMPS 2.0 Is Coming Down the Pipeline... Here's What to Expect!

[Iandefor]

As of late, I've been pondering the future of BUMPS. It's becoming big and kludgy and it's a bitch to maintain. Thinking about the potential benefits of just keeping the packages in a long list in the script itself and then maintaining a separate custom package function that needs to be updated with any changes to the main package list, there aren't many. If there's an error in package spelling, the entire release is rendered almost useless and the user has to manually download a new version of the script.

But metapackages don't suffer so badly from the above problems. Certainly, if a package is mispelled in a release, the release is useless. But if it's hosted on a repository the user has in sources.list, instead of needing to mitigate the problem by needing to post a bulletin on a forum the end user may or may not check (Hell, I don't look around here all that often and I'm the maintainer !) telling people not to use this or that version of the script, I can just fix it in the metapackage, update the repository, and the problem is solved.

So, BUMPS is going to be taking a new direction. While there won't be options to customize packages anymore, it's never been particularly necessary except for temporary workarounds. The majority of BUMPS will no longer be a script- it will be a metapackage. You could use it on its own if you manually enabled Seveas' repo and Universe/Multiverse. There would also be an option to automate setting up both Seveas' repo and Universe/Multiverse and install the metapackage via a script.

I have attached a first-look at the new script, which I'm going to name BUMPS 2.0. It's in alpha stage right now. Test it so I can make it better! Thanks!

EDITS:
Oh, and I know the popup at the start tells you to refer to the README. You can refer to it when I've written it . In the meantime, just give me feedback/bugs here.
Gaaah, and I know I'd said I'd have support for Broadcom Wifi setup in the next testing release I did... sorry, not as yet!

[angrylittleman]

Just used BUMPS 2.0 on a standard install. Worked without a hitch! Thanks!

[Iandefor]

Hey, feedback! Just what the doctor ordered. Thanks!

C'mon, people!

[bvanaerde]

It seems you forgot something: the script makes a copy of the original sources.list, but it doesn't put it back afterwards.

[Iandefor]

It seems you forgot something: the script makes a copy of the original sources.list, but it doesn't put it back afterwards.

I suppose I could have it do that, yeah.

Bloody users .

[bvanaerde]

I suppose I could have it do that, yeah.

Bloody users .

Hey, you're the one who wanted comments
The previous versions did this, if I remember it right.

For clarity, I'll outline what BUMPS does right here.

1. Back up /etc/apt/sources.list and replace it with a custom version
2. Install and configure a large set of multimedia-oriented packages
3. Offer to put the old sources.list back

Everything else seems to work very well though...

[Iandefor]

I've packaged up an alpha for everyone to test. Nothing much has changed (since nobody's really giving feedback), but I have re-enabled the ability to restore the old sources.list. See the attachment for the alpha.

[gigi1234]

The alpha version of BUMPS 2.0 worked flawlessly for me. I haven't tried the previous versions but running this version seemed to fix all my multimedia headaches.

Thanks to the developer of this tool.

[Iandefor]

BUMPS 2.0 Alpha 2 has been released. I've not made any substantive changes as yet, but have fixed it up so people on Edgy don't wind up using Dapper repositories .

[bvanaerde]

BUMPS 2.0 Alpha 2 has been released. I've not made any substantive changes as yet, but have fixed it up so people on Edgy don't wind up using Dapper repositories .

I'm trying out Edgy, so I might as well test BUMPS on it