"HEAD" means the latest revision published by whatever source code manager you are using. If Slashcode has moved to git and git is working (last time I tried, which was 6-10 months ago, git didn't work). I still think I have that repository, somewhere. If I do, I'll tar it and drop it to you via email.
<preface>I want to say against any future critiques: my goal is to be
a publisher. I want to run a large community discussion. I think the
moderation system of Slashdot, realized in whatever eventual form, is
the only one for my purposes.
It should be no surprise that I'm much more of an editor than a coder.
Ironically, though, the Slashcode community itself is in need of
reinvigoration, which makes someone like me perhaps more useful at the
moment than someone who can field-strip a Perl rifle.
Please consider me an enlightened end-user: ignorant of the necessary
minutiae, but educable. I'm not a developer. I don't yet understand
certain jargon. I'll need to ask questions that may seem idiotic or
pedantic to some. I ask your indulgence. (Since the community was all
but dead a few days ago, what has anyone still here got to lose by
letting me ask? The trail left by my questions will help and encourage
others like me.)</preface>
Shane -- Forgive my ignorance. When I go to
<https://sourceforge.net/projects/slashcode/files/Bundle-Slash>, I see
"Looking for the latest version? Download Bundle-Slash-2.52.tar.gz
(2.1 KB)". Then I see the litany of versions prior to 2.52.
I understand packages with version numbers. I don't understand what
you mean by version "HEAD", the "last SCM-Head," or where to go to
"get from src." Could you or someone explain?
On Sun, Feb 6, 2011 at 1:09 PM, Shane Zatezalo <firstname.lastname@example.org> wrote:
> Distro: CentOS
> Slash-version: HEAD (from src, never package)
> Don't use the 2.2.6, it is just *too* ancient to bother with. And the upgrade from 2.26 -> SCM-Head was just brutal. Work from the last SCM-Head.
> If I recall I'd start off buy getting perl, mod_perl and apache compiled togther and functionally running.
> While I was doing that, I'd (in another term window) install mySQL (and in another window) start installing CPAN modules (follow the cpan-instructions from slash-HEAD by the book).
> Once all that was done, I could make install and then 'install-slashsite' at will.
> On Feb 6, 2011, at 7:51 AM, George Taft wrote:
>> [...] let me ask those who are
>> still here:
>> The last time you successfully installed Slashcode so that it was up
>> and fully functional, what distro did you use, and what versions of
>> Perl, MySQL, Apache and...well, Slash? Was it actually 2.2.6, or was
>> it something from the repo?
>> For starters, I can tell you that on my second effort, it was Fedora
>> 14, Perl 5.12.3, MySQL 5.something, Apache 1.3.42, and Slash 2.52.
>> Anyone see any red flags?
>> We shouldn't expect anyone to want to use or support Slashcode when
>> the documentation to install it is half-missing. I'd like to figure
>> out what the latest of everything that work together for any given
>> Linux distro. I volunteer to write that documentation. I could use
>> your help.
>> Hey, how about let's start with: what are the specs of what Slashdot
>> itself is using right now?
>> == George
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
Slashcode-general mailing list