Define goals for version 1

[pior]

Project:

• Find a good project name (Find a better project name #71)

Features:

• Decent support for Python, Go, Ruby
  • python
  • go
  • ruby
• Support for Bash, Zsh
• Homebrew ([FEATURE] Introduces homebrew task #67)

Distribution:

• Solid (tested) install script Use Pytest and Pexpect for the integration tests #126
• Available on Homebrew
• Working Upgrade command

Other:

• Support for cloning plain git urls Support for cloning plain git urls #128

Documentation:

• Gif terminal showing an example of the up command
• Doc about all commands
• Doc about all up tasks
• Doc about all managed environments

[pior]

Ping @mlhamel

[mlhamel]

I think we should also take a decision regarding the name of the project for this first official release.

[merwok]

Can I add: support apt installs? Many devs are on Debian or derived systems.

[pior]

We didn't update this milestone for many months (even through progress have been made).

DevBuddy should work perfectly on Linux, supporting Apt packages seems totally relevant.

I will try to setup a Github project instead of refreshing this issue.

[pior]

@merwok do you want to create an issue for apt ?

[pior]

Project: https://github.com/devbuddy/devbuddy/projects/1

[mlhamel]

Just wondering, is there any way for us to support in the same project either osx or linux? very often you don't care about apt or brew, you just want to be sure libxml2 is installed by example.

[merwok]

Package names are often different on Homebrew / Debian APT repos / Ubuntu APT repos / yum repos / AUR: libxml2-dev vs libxml2-devel vs devel/libxml2

That’s why the first idea was independent clauses:

 up:
   - homebrew:
     - somelib
   - apt:
     - somelib12

I think freedesktop has a system to convert dependencies between Fedora, Debian, Ubuntu, etc. With that, you could imagine a universal up: { os-packages: [ somelib ] }, but it could be a lot of work, and I don’t know that it would handle MacOS.

[pior]

@merwok Interesting, do you have a link to the FreeDesktop system you mention?

[merwok]

https://www.freedesktop.org/software/appstream/docs/chap-AppStream-About.html

[pior]

I think having tasks specific to some OS is a middle ground. There will be no magic behind.

A task could just declare some "activation" conditions.
Maybe the UI would still show the task with a mention that it was skipped.

[merwok]

That seems ok for v1! Users will say if the messages are confusing.