Re: [Slashcode-general] Minimum version of every component for a successful Slash install?

[Shane Z. <sh...@lo...>]

I vote put it on github.

I did this:

git clone git://slashcode.git.sourceforge.net/gitroot/slashcode/slashcode

per the info I found on this:

http://sourceforge.net/projects/slashcode/develop

and rec'd the "nonexistent ref" which I believe is the same problem with their repo that existed in 2009. Sadly, even the browse-code is broke: http://slashcode.cvs.sourceforge.net/slashcode

I'm fairly certain I've got a checkout somewhere of the slashcode-head as it was immediately before they stopped committing to it. I'll look around. If I find it I'll throw it up on Github.

 Shane

PS Actual output:

coolio:tmp shane$ git clone git://slashcode.git.sourceforge.net/gitroot/slashcode/slashcode
Cloning into slashcode...
remote: Counting objects: 93881, done.
remote: Compressing objects: 100% (21517/21517), done.
remote: Total 93881 (delta 69417), reused 93881 (delta 69417)
Receiving objects: 100% (93881/93881), 14.93 MiB | 696 KiB/s, done.
Resolving deltas: 100% (69417/69417), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.



On Feb 6, 2011, at 4:33 PM, George Taft wrote:

> Cliff, thanks for the explanation, and the offer. Shane, thanks for
> the advice on the Slash component of an install.
> 
> When I get a copy of the repository that Cliff offered, I will try to
> document unambiguously my effort to make an install from scratch on a
> stock install of CentOS 5.5.
> 
> I admit that I don't really get Git in the first place. Even so, it
> seems to me that the overall benefit on the Slashcode project of the
> move to Git was, shall we say, less than optimal? I wonder what others
> think, and how a future fork of the project should conduct itself.
> 
> == George
> 
> On Sun, Feb 6, 2011 at 3:49 PM, Clifton Wood <cli...@gm...> wrote:
>> "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.
>> - Cliff
>> On Sun, Feb 6, 2011 at 3:06 PM, George Taft <geo...@gm...> wrote:
>>> 
>>> <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?
>>> 
>>> == George
>>> 
>>> 
>>> On Sun, Feb 6, 2011 at 1:09 PM, Shane Zatezalo <sh...@lo...> 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.
> 
> ------------------------------------------------------------------------------
> 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? 
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general