|Once again, I vote for curl! And, I think the binaries should have Quarks pre-loaded, ready to go.|
And, I think the next US presidential election needs to happen now. But I understand there are constitutional limits there... so I'll settle for UGens in Quarks with easy download.
On Dec 11, 2007, at 7:08 PM, James Harkins wrote:
I've thought further and I agree now that requiring svn to get quarks is a hassle for new users. Would be nice to have another option for 3.2.
Is this likely to happen? I'll contribute but I hesitate to change anything if there's no decision yet on the right direction.
On Dec 1, 2007, at 6:38 PM, Scott Wilson wrote:
Well, easy updating is one of the points of a package manager. I see no reason not to include the current state of quarks as an optional install with releases. (We could have a release with and without...) If they've changed since a release, update.
Most quarks are pretty small, and they'll be even smaller without .svn folders. I don't think this would make a big difference in download times or resources.
On 1 Dec 2007, at 23:21, Click Nilson wrote:
There was also the issue of having access to stuff even offline, and perhaps all quarks plus other third party stuff (like Crucial lib) could reside within an 'extras' directory in the main SuperCollider directory and be part of a standard download. These wouldn't be installed by default but the symbolic links system from Quarks could be used as needed. I guess the additional issue would be the bloat of this content and additional size of downloads all at once.
Perhaps quarks stay quarks, but there is a straight download option rather than dependence on SVN; named release builds of Quarks, like sc-plugins3.1? Download and install yourself in the official Quarks directory location? I know SVN might make all this seem clever and well managed, but there will always be many users who don't want SVN but do want the Arduino classes for example...
Perhaps there are some solutions I'm not seeing...
On 1 Dec 2007, at 22:36, Scott Wilson wrote:
Coming back to this topic... (It came up again off-list in relation to the book, 3.2, etc.)
If we're going to need to use curl or something like this for ugens I have to wonder if it might make sense to use that for all Quarks, and remove the user svn dependancy (and thus hopefully solve that issue). svn is of course great for Quarks development, but seems to me maybe a bit overkill for use as simple package manager.
Maybe curl (and perhaps something pythonish for the windows port) would make more sense? Or something similar.
: H. James Harkins
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
Sc-devel mailing list
/* Joshua D. Parmenter
“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono*/