Adding Linux support #659
Comments
+1 |
1 similar comment
👍 |
👍 I'd support this as well, as already mentioned in the PR, but for this to happen someone from github would have to take part in this discussion. Since I don't know exactly how boxen works please educate me if anything I say is stupid :) You want to keep github/boxen and telamonian/boxen-linux separate, right? Why not have a cross platform github/boxen first and then see if it is feasible to have a cross platform github/our-boxen? |
Supporting multi-platform Boxen is a large project, from both an initial implementation point of view, but more importantly from a maintenance point of view. None of the Boxen maintainers use Linux as their primary desktop operating system, and adding a second "supported" OS makes change significantly slower and more difficult. Unless someone can come up with a proposal which mitigates those two maintenance issues, I'd be very hesitant to support Linux. Now, please don't get me wrong here; I'd love to see these issues resolved, but I am not personally motivated to address them right now with so many other issues on the list. If you folks want to take that on, I will definitely take any proposals seriously! |
Think @dgoodlad put it well. Let's close this issue and for people who want to make this happen, submit PRs. |
I agree with @dgoodlad and @seanknox, @telamonian please feel free to open PRs if you'd like to see this happen! |
+1 |
What is the current thinking amongst the Boxen dev team, and the wider Boxen using community, about adding support for Linux to Boxen? I myself have been working on something along these lines (see telamonian/our-boxen/tree/add-linux-support). I submitted a related pull request (pull #651) in an attempt start a discussion about Boxen-Linux (or whatever you want to call it), but I realize that I may have gone about this kind of backwards and am now attempting to start a discussion by actually starting a discussion. I would greatly appreciate hearing everyone's thoughts on the subject.
The text was updated successfully, but these errors were encountered: