Prefconfigured Dtella + DC++ client

[amoghbl1]

Configured dtella and dc++ client that ships together in order to make it super simple for users to install and use.

[nehaljwani]

I don't like this. People should be able to read the instructions and do stuff. No spoon-feeding.

[amoghbl1]

That's true for people who are in our college and well, our network. It would be a great learning experience if they set it up themselves. But this project, what I think, is not just targeted at users from our college, in the future, other colleges/networks might also use it and in case they do, most of that college might lack the technical ability to make these configurations and hence, by doing this, we would make this software really easy to promote and use, and at the end of the day, that's what we want right, more people yo use it!

[ffledgling]

I'm sort of with @nehaljwani on this, but for different reasons. I think letting people use their own DC client of choice is a lot more flexible than forcing everyone to use a particular client. Pre-packaging a client might possibly also cause other legal issues (Licences don't match, Owners of the Client software don't give their consent etc.).

If simplicity is the goal, I think it might be better served by transforming dtella into a daemon that can run in the background similar to other linux services such as httpd, sshd etc. (ASIDE: need to figure out if this is viable on Windows). Packaging dtella into .RPMs and .DEBs should also take us towards the same goal. There's already code to create .DMGs for OSX.

An extension of this might be to use Travis-CI to autobuild these install packages whenever there's a new release.

[nehaljwani]

I don't think Windows builds are fully supported by Travis.
In Windows, dtella runs as daemon by default. The installer itself gives
the option to start it on boot.

On Mon, Mar 9, 2015 at 4:35 AM, Anhad Jai Singh notifications@github.com
wrote:

I'm sort of with @nehaljwani https://github.com/nehaljwani on this, but
for different reasons. I think letting people use their own DC client of
choice is a lot more flexible than forcing everyone to use a particular
client. Pre-packaging a client might possibly also cause other legal issues
(Licences don't match, Owners of the Client software don't give their
consent etc.).

If simplicity is the goal, I think it might be better served by
transforming dtella into a daemon that can run in the background similar to
other linux services such as httpd, sshd etc. (ASIDE: need to figure out if
this is viable on Windows). Packaging dtella into .RPMs and .DEBs should
also take us towards the same goal. There's already code to create .DMGs
for OSX.

An extension of this might be to use Travis-CI to autobuild these install
packages whenever there's a new release.

—
Reply to this email directly or view it on GitHub
#10 (comment).

Nehal J Wani

[amoghbl1]

Oh ya, licenses! Well, the other points you make are sensible as well,
daemon sounds cool!
On Mar 9, 2015 12:05 AM, "Anhad Jai Singh" notifications@github.com wrote:

I'm sort of with @nehaljwani https://github.com/nehaljwani on this, but
for different reasons. I think letting people use their own DC client of
choice is a lot more flexible than forcing everyone to use a particular
client. Pre-packaging a client might possibly also cause other legal issues
(Licences don't match, Owners of the Client software don't give their
consent etc.).

If simplicity is the goal, I think it might be better served by
transforming dtella into a daemon that can run in the background similar to
other linux services such as httpd, sshd etc. (ASIDE: need to figure out if
this is viable on Windows). Packaging dtella into .RPMs and .DEBs should
also take us towards the same goal. There's already code to create .DMGs
for OSX.

An extension of this might be to use Travis-CI to autobuild these install
packages whenever there's a new release.

—
Reply to this email directly or view it on GitHub
#10 (comment).