From: George T. <geo...@gm...> - 2011-02-06 12:51:14
|
So I've made two attempts to install Slashcode on a virtualized server. I can install any number of different distros. I've tried CentOS 5.5 and Fedora 14, and crucial functionality seems to be missing by the time I get done with Slash. (In the former case, I couldn't see how to post comments; in the latter, I couldn't post comments or stories, or manage users.) My ability to manage an install is not strong. I may be making bonehead mistakes. Or I may be using components that are too new. Before I conclude that's a matter of PEBCAK, 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 |
From: Shane Z. <sh...@lo...> - 2011-02-06 18:32:21
|
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? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |
From: George T. <geo...@gm...> - 2011-02-06 20:06:10
|
<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. > > 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 |
From: Clifton W. <cli...@gm...> - 2011-02-06 20:49:47
|
"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. > > > > 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? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > |
From: George T. <geo...@gm...> - 2011-02-06 21:33:53
|
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. |
From: Shane Z. <sh...@lo...> - 2011-02-07 03:02:23
|
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 |
From: Marc G. F. <sc...@hu...> - 2011-02-07 15:27:15
|
On Sun, 6 Feb 2011, Shane Zatezalo wrote: > 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 See note from Jamie, but not a problem, just a mis-understanding on what hte error means :( So we do have a good starting point on this ... > > 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 > > > ------------------------------------------------------------------------------ > 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 > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Shane Z. <sh...@lo...> - 2011-02-07 16:03:36
|
Yes, I saw Jamie's comment. Consequently, I went and grabbed the newer code via SF, and merged it w/ the repo that I created on github. I think, given the fact that we now now how to access the newer stuff on SF.Net, the need for the repo I created on Github is gone. I'll leave it be for a day or two, incase someone wants to pull from it, just to get the latest in a simple pull, but then I think I'm going to delete the repo entirely. On Feb 7, 2011, at 10:27 AM, Marc G. Fournier wrote: > On Sun, 6 Feb 2011, Shane Zatezalo wrote: > >> 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 > > See note from Jamie, but not a problem, just a mis-understanding on what hte error means :( So we do have a good starting point on this ... > > >> >> 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 >> >> >> ------------------------------------------------------------------------------ >> 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 >> > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > sc...@hu... http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Marc G. F. <sc...@hu...> - 2011-02-07 16:05:56
|
On Mon, 7 Feb 2011, Shane Zatezalo wrote: > > Yes, I saw Jamie's comment. Consequently, I went and grabbed the newer > code via SF, and merged it w/ the repo that I created on github. I > think, given the fact that we now now how to access the newer stuff on > SF.Net, the need for the repo I created on Github is gone. I'll leave it > be for a day or two, incase someone wants to pull from it, just to get > the latest in a simple pull, but then I think I'm going to delete the > repo entirely. NOpe, we need the new one ... the old one, we cannot commit to, so its static ... if we are going to do work on it, and create proper releases, we need someting we can commit to ... > > > On Feb 7, 2011, at 10:27 AM, Marc G. Fournier wrote: > >> On Sun, 6 Feb 2011, Shane Zatezalo wrote: >> >>> 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 >> >> See note from Jamie, but not a problem, just a mis-understanding on what hte error means :( So we do have a good starting point on this ... >> >> >>> >>> 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 >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> >> >> ---- >> Marc G. Fournier Hub.Org Hosting Solutions S.A. >> sc...@hu... http://www.hub.org >> >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... > > > ------------------------------------------------------------------------------ > 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 > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Marc G. F. <sc...@hu...> - 2011-02-07 20:33:02
|
Shane ... What did you call the repo on github? how do we access it? On Mon, 7 Feb 2011, Marc G. Fournier wrote: > On Mon, 7 Feb 2011, Shane Zatezalo wrote: > >> >> Yes, I saw Jamie's comment. Consequently, I went and grabbed the newer code >> via SF, and merged it w/ the repo that I created on github. I think, given >> the fact that we now now how to access the newer stuff on SF.Net, the need >> for the repo I created on Github is gone. I'll leave it be for a day or >> two, incase someone wants to pull from it, just to get the latest in a >> simple pull, but then I think I'm going to delete the repo entirely. > > NOpe, we need the new one ... the old one, we cannot commit to, so its static > ... if we are going to do work on it, and create proper releases, we need > someting we can commit to ... > > > >> >> On Feb 7, 2011, at 10:27 AM, Marc G. Fournier wrote: >> >>> On Sun, 6 Feb 2011, Shane Zatezalo wrote: >>> >>>> 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 >>> >>> See note from Jamie, but not a problem, just a mis-understanding on what >>> hte error means :( So we do have a good starting point on this ... >>> >>> >>>> >>>> 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 >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>> >>> ---- >>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>> sc...@hu... http://www.hub.org >>> >>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >> >> >> >> ------------------------------------------------------------------------------ >> 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 >> > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > sc...@hu... http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Shane Z. <sh...@lo...> - 2011-02-07 21:23:00
|
https://github.com/lottadot/slashcode via git read only git clone git://github.com/lottadot/slashcode.git via http read only git https://lot...@gi.../lottadot/slashcode.git via ssh git clone gi...@gi...:lottadot/slashcode.git I did delete the repo off github, and re-created it early this morning, straight from their git-repo-head (rather then what I had, yesterday). That way it has the commit history intact. The branch 'live' is the same as well. Theoretically work could be done via github, and the slashcode team could selectively-pull from the github repo. Here are the commands I exec'd to get it (YMMV): $ git clone gi...@gi...:lottadot/slashcode.git slashcode-github $ cd slashcode-github/ $ git checkout live Already on 'live' $ git branch live Shane On Mon, Feb 7, 2011 at 3:32 PM, Marc G. Fournier <sc...@hu...> wrote: > > Shane ... > > What did you call the repo on github? how do we access it? > > On Mon, 7 Feb 2011, Marc G. Fournier wrote: > >> On Mon, 7 Feb 2011, Shane Zatezalo wrote: >> >>> >>> Yes, I saw Jamie's comment. Consequently, I went and grabbed the newer >>> code via SF, and merged it w/ the repo that I created on github. I think, >>> given the fact that we now now how to access the newer stuff on SF.Net, the >>> need for the repo I created on Github is gone. I'll leave it be for a day or >>> two, incase someone wants to pull from it, just to get the latest in a >>> simple pull, but then I think I'm going to delete the repo entirely. >> >> NOpe, we need the new one ... the old one, we cannot commit to, so its >> static ... if we are going to do work on it, and create proper releases, we >> need someting we can commit to ... >> >> > >>> >>> On Feb 7, 2011, at 10:27 AM, Marc G. Fournier wrote: >>> >>>> On Sun, 6 Feb 2011, Shane Zatezalo wrote: >>>> >>>>> 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 >>>> >>>> See note from Jamie, but not a problem, just a mis-understanding on what >>>> hte error means :( So we do have a good starting point on this ... >>>> >>>> >>>>> >>>>> 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 >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> 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 >>>>> >>>> >>>> ---- >>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>>> sc...@hu... http://www.hub.org >>>> >>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> >> >> ---- >> Marc G. Fournier Hub.Org Hosting Solutions S.A. >> sc...@hu... http://www.hub.org >> >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >> > > ---- > Marc G. Fournier Hub.Org Hosting Solutions S.A. > sc...@hu... http://www.hub.org > > Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... > |
From: Marc G. F. <sc...@hu...> - 2011-02-07 21:31:15
|
'k, since SlashCode belongs to the Slashdot folks, we need to rename th efork ot someting different ... I want like to somehow keep some sort of 'history in the name' ... anyone got better then SlashTNG? PortalSC (SC == Slashcode)? Something better ... ? On Mon, 7 Feb 2011, Shane Zatezalo wrote: > https://github.com/lottadot/slashcode > > via git read only git clone git://github.com/lottadot/slashcode.git > via http read only git https://lot...@gi.../lottadot/slashcode.git > via ssh git clone gi...@gi...:lottadot/slashcode.git > > I did delete the repo off github, and re-created it early this > morning, straight from their git-repo-head (rather then what I had, > yesterday). That way it has the commit history intact. The branch > 'live' is the same as well. Theoretically work could be done via > github, and the slashcode team could selectively-pull from the github > repo. > > Here are the commands I exec'd to get it (YMMV): > > $ git clone gi...@gi...:lottadot/slashcode.git slashcode-github > $ cd slashcode-github/ > $ git checkout live > Already on 'live' > $ git branch live > > Shane > > On Mon, Feb 7, 2011 at 3:32 PM, Marc G. Fournier <sc...@hu...> wrote: >> >> Shane ... >> >> What did you call the repo on github? how do we access it? >> >> On Mon, 7 Feb 2011, Marc G. Fournier wrote: >> >>> On Mon, 7 Feb 2011, Shane Zatezalo wrote: >>> >>>> >>>> Yes, I saw Jamie's comment. Consequently, I went and grabbed the newer >>>> code via SF, and merged it w/ the repo that I created on github. I think, >>>> given the fact that we now now how to access the newer stuff on SF.Net, the >>>> need for the repo I created on Github is gone. I'll leave it be for a day or >>>> two, incase someone wants to pull from it, just to get the latest in a >>>> simple pull, but then I think I'm going to delete the repo entirely. >>> >>> NOpe, we need the new one ... the old one, we cannot commit to, so its >>> static ... if we are going to do work on it, and create proper releases, we >>> need someting we can commit to ... >>> >>>> >>>> >>>> On Feb 7, 2011, at 10:27 AM, Marc G. Fournier wrote: >>>> >>>>> On Sun, 6 Feb 2011, Shane Zatezalo wrote: >>>>> >>>>>> 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 >>>>> >>>>> See note from Jamie, but not a problem, just a mis-understanding on what >>>>> hte error means :( So we do have a good starting point on this ... >>>>> >>>>> >>>>>> >>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> 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 >>>>>> >>>>> >>>>> ---- >>>>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>>>> sc...@hu... http://www.hub.org >>>>> >>>>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>> >>> ---- >>> Marc G. Fournier Hub.Org Hosting Solutions S.A. >>> sc...@hu... http://www.hub.org >>> >>> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >>> >> >> ---- >> Marc G. Fournier Hub.Org Hosting Solutions S.A. >> sc...@hu... http://www.hub.org >> >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... >> > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Larson, T. E. <TEL...@we...> - 2011-02-07 21:48:04
|
> 'k, since SlashCode belongs to the Slashdot folks, we need to rename th > efork ot someting different ... I want like to somehow keep some sort of > 'history in the name' ... anyone got better then SlashTNG? PortalSC (SC > == Slashcode)? Something better ... ? Backslash (Slash is back)? Solidus (the typography geek in me comes out)? Tim -- Tim Larson App Admin, Intercall Production Services |
From: Marc G. F. <sc...@hu...> - 2011-02-07 23:35:02
|
As far as domains are concerned, both are already taken ... :( On Mon, 7 Feb 2011, Larson, Timothy E. wrote: >> 'k, since SlashCode belongs to the Slashdot folks, we need to rename th >> efork ot someting different ... I want like to somehow keep some sort of >> 'history in the name' ... anyone got better then SlashTNG? PortalSC (SC >> == Slashcode)? Something better ... ? > > Backslash (Slash is back)? > > Solidus (the typography geek in me comes out)? > > > Tim > -- > Tim Larson > App Admin, Intercall Production Services > > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Larson, T. E. <TEL...@we...> - 2011-02-08 15:41:30
|
> > Backslash (Slash is back)? > > > > Solidus (the typography geek in me comes out)? > As far as domains are concerned, both are already taken ... :( If you like the name Foo but can't get the domain Foo.TLD, you can always go for FooProject.TLD. Tim -- Tim Larson App Admin, Intercall Production Services |
From: Marc G. F. <sc...@hu...> - 2011-02-14 15:35:54
|
okay, this definitely helps ... time to do some code tracing, see if I can't figure out what is breaking, and where ... it either in the sql query, or in the caching ... On Mon, 14 Feb 2011, Shane Zatezalo wrote: > As for caching: Slashcode isn't designed to be constantly restarted over and over to add things. It's designed for stability and uptime. Caching is done via the Slash object (ie within Apache), minimally, and then they use memcached, and eventually mysql's own caching. So you would tend to either: > > 1) attach a file to a story > 2) put a file into images.example.com and reference it in your story > 3) create your own theme, put that into your own SCM repo, install the slashsite using your theme. then reference the file(s) via html/css. test/rinse, repeat, when it's done you deploy to production. when your theme gets an update, you run make install on all webheads/fileservers involved. > > As for blocks/portals: I'm sorry, I don't remember. It's been too long. I do recall they were confusing to me, too. Google it there's got to be prior discussions about it out there. > > Ordernum: is how the ORDER BY .... is done. > > Looking at your screenshot, the skin, the type, and the block_id I recall being pertinent. Because you could set a block to show in more then one skin. I do not remember why there is a pulldown that has 'portald' as allowable value for 'type', but then a 'portal' checkbox, too. > > Shane > > > On Feb 11, 2011, at 9:59 PM, Marc G. Fournier wrote: > >> >> Okay, there has gotta be a few things I'm missing here that are obvious to soemone that has used this extensively ... >> >> 1. where are files cached? Do I seriously have to restart the apache server each and every time I make a change, or is there a file I can touch / remove on the file system to force it to reload? >> >> 2. how do blocks / portals work? For instance, I just changed a single value in Blocks -> poll: OrderNum from 2 -> 3 ... not the poll is gone .. change it back to 2, and its *still* gone ... I've even tried restarting the web servrer, jsut in case ti was cached somewhere in there, and nothing ... >> >> 3. and what *is* the Ordernum? Can two portals have the same Ordernum? >> >> All I want to do right now is getting a portal/RSS feed in place that will pull in thte commit messages from Git ... the portal seems to be right, but I can't get it to display ... :( see http://hub.org/~scrappy/haxlash.png to see how I have it setup, and please point me to the errors in my knowlege :( >> >> >> >> ---- >> Marc G. Fournier Hub.Org Hosting Solutions S.A. >> sc...@hu... http://www.hub.org >> >> Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... > > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Jamie M. <ja...@mc...> - 2011-02-14 17:04:17
|
On Feb 14, 2011, at 10:35 AM, Marc G. Fournier wrote: >> On Feb 11, 2011, at 9:59 PM, Marc G. Fournier wrote: >> >>> Okay, there has gotta be a few things I'm missing here that are obvious to soemone that has used this extensively ... >>> >>> 1. where are files cached? Do I seriously have to restart the apache server each and every time I make a change, or is there a file I can touch / remove on the file system to force it to reload? By default, mod_perl will notice your .pl files changing and reimport them. If you want changes to your .pm files also to be reimported, and are willing to pay the performance penalty, check out Apache::Reload: <http://perl.apache.org/docs/1.0/guide/porting.html#Using_Apache__Reload> Templates are written from disk into the DB by template-tool, and edited in the DB at runtime by a couple places in Slash, including the admin template editing pages. If you're editing templates on disk, I guess the DB would be a "cache" of that which you flush by running template-tool. Apache also keeps its own cache of the templates in the DB, grep on template_cache_size for more on that. -- Jamie McCarthy jam...@gm... ja...@mc... 269-267-2008 |