Remove debian package information #169

Closed
wants to merge 1 commit into
from

3 participants

@josegonzalez

This is not a StatsD concern. Refs #161

@josegonzalez josegonzalez Remove debian package information
This is not a StatsD concern. Refs #161
e4d378e
@mrtazz
Etsy, Inc. member

I agree it's not a StatsD main concern, but it still serves as a useful example I think. And just because there is no documentation included, doesn't mean it should be removed completely.

@mrtazz mrtazz closed this Oct 20, 2012
@josegonzalez
@loganfuller

Just to put in my two cents - it's comments like josegonzalez's that make people avoid open source. The entire point of a package is to allow people unable or unwilling to dedicate their time to learning such a specific workflow as creating a Debian package to still derive use from the software. I strongly agree that the package info should remain.

@josegonzalez

@loganfuller Thanks for commenting on a 5 month old, closed pull request.

My original pull request was meant to be a tongue-in-cheek remark about the fact that, while we do have some of the requirements for a debian package, there is no usage documentation for that.

I intended on replacing our own statsd version - which broke due to a ruby upgrade - with etsy's statsd, but the installation documentation left something to be desired. Should I install an old tag? Should I just clone the repo as the docs say? How do I go about updating (if at all)? That is extremely unfriendly to someone who wants to use the software.

Yes, I get the point of having the package info there, but there are a few problems with the etsy developer's stance on it:

  • Does this mean we ignore all other packaging attempts? Should we include Redhat or Arch packaging information?
  • Given that at some point the resources were deemed good enough to add to the repo, can whoever made that commit provide a small - not even necessarily complete - guide as to how to use the package info to create a package?

The entire point of a package is to allow people unable or unwilling to dedicate their time to learning such a specific workflow as creating a Debian package to still derive use from the software.

I can still derive use from the software without debian packaging info - which might even be unmaintained given the fact that there is no one actively stating "here is how we package it, find and report bugs everyone!" in the readme - so what is the point of it?

At least one etsy developer has said it wasn't their responsibility to maintain a debian package, and this I agree with. Given that they do not want to maintain a debian package - which is totally their choice - I decided that maybe they should just remove the debian info from the repo, so as not to cause issues when new developers stumble upon it, hoping that there is a package they can just wget and install.

In any case, the pull request is closed, and there is no point to either of our comments, except to waste time and annoy anyone watching this repository via email.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment