Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Suggestion (Install,Update,Upgrade,...) #135

Open
sameermw opened this issue Jul 23, 2014 · 5 comments
Open

Feature Suggestion (Install,Update,Upgrade,...) #135

sameermw opened this issue Jul 23, 2014 · 5 comments

Comments

@sameermw
Copy link

If Betty can run following commands or it would be grate...

betty update system / betty run update --- > (apt-get update)
betty upgrade system --- > (apt-get upgrade)
betty dist-upgrade --- > (dist-upgrade)
betty install <package_name> --- > (apt-get install)
betty remove <package_name> --- > (apt-get remove)

@Tamsyn
Copy link

Tamsyn commented Jul 25, 2014

It would be cool if betty could use more linux friendly players like rhythmbox and clementine as well as itunes.

So for example - betty run rhythmbox
and then all the play, next song, etc, commands will refer to rhythmbox.

@thatrandomcanadianguy
Copy link

The only problem with the first idea is that the developers would probably need to find away to make this system-agnostic for the other Linux distro's like SUSE,Red Hat, and Arch which don't use APT as a package manager.

@brysgo
Copy link
Collaborator

brysgo commented Jul 30, 2014

Maybe someone should build a cross platform package manager proxy and we could use it.

@thatrandomcanadianguy
Copy link

How would you go about doing something like that?

@brysgo
Copy link
Collaborator

brysgo commented Aug 5, 2014

  1. First I would read the manual for each package manager that needs to be supported.
  2. Then I would make a list of use cases I wanted to cover.
  3. Figure out how to accomplish each task with each package manager.
  4. Write a common package manager interface that maps easily to each package manager.
  5. Write mappings from the common interface to each individual package manager.
  6. Write something to detect which package manager is present and use the correct mapping.

For this use case I wouldn't worry about standardizing package names since the user would be responsible for getting the package name right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants