[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]

Re: [EMACSPEAK The Complete Audio Desktop] Emacspeak Development Is Moving To GitHub



good catch -- I'm still going through the Makefile and cleaning
up stuff -- the sawfish stuff will indeed go away from the
install rules. 
>>>>> "Steve" == Steve Holmes <steve@xxxxxxxxxxx> writes:
    Steve> Actually, I have a package build script now that pulls
    Steve> most current version of emacspeak from the new git
    Steve> repo. So that part is coming along but I do have
    Steve> another problem however...
    Steve> 
    Steve> During the "make install", I get errors about
    Steve> sawfish/*.jl not being found. When I looked around a
    Steve> bit, I noticed that the sawfish stuff is in obsolete
    Steve> now. Shouldn't the install: recipe be modified to not
    Steve> install sawfish?
    Steve> 
    Steve> On Tue, Mar 10, 2015 at 07:34:54PM -0700, T. V. Raman
    Steve> wrote:
    >> the emacspeak-svn package you are likely refering to on
    >> github was a mirror of the googlecode svn repo that
    >> someone else had created. Am sure things will catch up
    >> once the announcement has perculated through the various
    >> networks. >>>>> "Steve" == Steve Holmes
    >> <steve@xxxxxxxxxxx> writes:
    Steve> This is good news indeed. I like git but could learn a
    Steve> lot more about development in a git environment.
    Steve> 
    Steve> Note to Arch Linux users: I plan to build an
    Steve> emacspeak-git package to place in the AUR within the
    Steve> next day or so. This will make it easier for Arch
    Steve> package users to pull emacspeak from git in the
    Steve> future. Someone else owns the emacspeak-svn package in
    Steve> AUR but I would think that package would eventually go
    Steve> away since svn will no longer be used here.
    Steve> 
    Steve> Thanks again for such a neat package for emacs.
    Steve> 
    Steve> On Mon, Mar 09, 2015 at 03:39:08PM +0000, T. V. Raman
    Steve> wrote:
    >> >> Emacspeak Development Is Moving To GitHub
    >> >> 
    >> >> 
    >> >> 1 Summary:
    >> >> 
    >> >> 
    >> >> Emacspeak development is moving from Google Code
    >> Hosting >> to GitHub. If you have been running from the
    >> SVN >> repository, I recommend you switch to the GitHub
    >> version >> by executing:
    >> >> 
    >> >> 
    >> >> git clone https://github.com/tvraman/emacspeak.git make
    >> >> config make -j
    >> >> 
    >> >> 
    >> >> 
    >> >> If using Outloud TTS:
    >> >> 
    >> >> 
    >> >> cd servers/linux-outloud && make
    >> >> 
    >> >> 
    >> >> 
    >> >> If using Espeak TTS:
    >> >> 
    >> >> 
    >> >> cd servers/linux-espeak && make
    >> >> 
    >> >> 
    >> >> 
    >> >> After this, all you should need to stay up to date is a
    >> >> periodic
    >> >> 
    >> >> 
    >> >> git pull; make config; make
    >> >> 
    >> >> 
    >> >> 2 A Brief History
    >> >> 
    >> >> 
    >> >> 
    >> >> The first five years of Emacspeak development used a
    >> local >> RCS repository on my home machine (1994
    >> -1999). The first >> few releases of Emacspeak were
    >> distributed through the Web >> site and FTP server at
    >> Digital Research; they were also >> mirrored at
    >> Cornell. After moving to Adobe Systems in the >> fall of
    >> 1995, Emacspeak was distributed exclusively >> through my
    >> Web page on the Cornell CS Department Web >> server, which
    >> also hosted my personal Web site. In 2000, I >> created
    >> Emacspeak On SourceForge
    >> >> 
    >> >> and used that site for both hosting the Emacspeak
    >> source >> code as well as the Web site -- coincidentally,
    >> I lost the >> ability to update my Web site at Cornell CS
    >> around the >> same time.
    >> >> 
    >> >> 
    >> >> Over time it became harder and harder to publish new >>
    >> Emacspeak releases through the SourceForge >>
    >> interface. Luckily, Google Code Hosting came along a few
    >> >> months after I joined Google, and moving the source
    >> code >> repository to Google Code SVN was a no-brainer. My
    >> friend >> and colleague Fitz helped me migrate the 5+
    >> years of CVS >> history to SVN; this meant that the source
    >> code repository >> on Google Code also recorded all of the
    >> development >> history that had been built up on
    >> Sourceforge. Now, it's >> time to move to GitHub. I've
    >> been using Git for most of my >> work the last few years,
    >> but was simply too lazy to move >> Emacspeak development
    >> from SVN to Git on GoogleCode. But >> over time, the
    >> advantages present in Git as a source >> control system
    >> and GitHub as a hosting service have >> increased --
    >> primary among these -- a rich set of Emacs >> tools that
    >> have been written to leverage the GitHub >> API. For Git
    >> integration in Emacs, my personal preference >> is package
    >> Magit available through Elpa --
    >> >> 
    >> >> 
    >> >> Mx package-install magit in Emacs.
    >> >> 
    >> >> 
    >> >> 
    >> >> The GitHub Web site itself is fairly heavy-weight in
    >> terms >> of its use of scripting, ie performing all
    >> operations >> through the github.com Web site from within
    >> Emacs is >> fairly unpleasant. But the afore-mentioned
    >> GitHub API >> makes this a non-issue at this point with
    >> respect to the >> type of workflow I prefer. So this week,
    >> I did the work to >> migrate Emacspeak development to
    >> Emacspeak On GitHub.
    >> >> 
    >> >> 
    >> >> 3 Status Of Migration
    >> >> 
    >> >> 
    >> >> 
    >> >> With help from some of the kind folk at Google Code >>
    >> Hosting, I've successfully migrated the source code >>
    >> repository including all release tags to GitHub. I am now
    >> >> checking in changes into GitHub; the SVN repository on
    >> >> Google Code Hosting is now frozen, and I do not plan to
    >> >> make any commits there. I presently have no immediate
    >> >> plans to start using features of GitHub like the Issue
    >> >> Tracker; for now we will continue to use the Emacspeak
    >> >> mailing list which has served us well for 20 years. I
    >> have >> also taken this opportunity to prune out legacy
    >> portions >> of the Emacspeak codebase by moving modules to
    >> obsolete at >> each level of the directory tree. Since
    >> starting the >> Emacspeak Blog in late 2005, I have
    >> published a sequence >> of articles describing Emacspeak
    >> features and usage >> patterns; I felt that having these
    >> articles for local >> reference made a useful supplement
    >> to the emacspeak online >> documentation. Toward this end,
    >> I have downloaded all >> articles published so far and
    >> checked in both XML and HTML >> versions into
    >> sub-directory blogs. Note that newer >> articles are also
    >> available as .org files under >> sub-directory
    >> announcements.
    >> >> 
    >> >> 
    >> >> 4 Next Steps
    >> >> 
    >> >> 
    >> >> 
    >> >> I still need to learn how to do software releases on >>
    >> GitHub.
    >> >> 
    >> >> Share And Enjoy!
    >> >> 
    >> >> 
    >> >> Date: <2015-03-06 Fri>
    >> >> 
    >> >> Author: raman
    >> >> 
    >> >> Created: 2015-03-07 Sat 08:12
    >> >> 
    >> >> Emacs 25.0.50.1 (Org mode 8.2.10)
    >> >> 
    >> >> Validate
    >> >> 
    >> >> 
    >> >> 
    >> >> 
    >> >> --
    >> >> Posted By TV Raman to EMACSPEAK The Complete Audio
    >> Desktop >> at 3/09/2015 08:39:00 AM
    Steve> 
    Steve> -----------------------------------------------------------------------------
    Steve> To unsubscribe from the emacspeak list or change your
    Steve> address on the emacspeak list send mail to
    Steve> "emacspeak-request@xxxxxxxxxxx" with a subject of
    Steve> "unsubscribe" or "help".
    Steve> 
    Steve> -----------------------------------------------------------------------------
    Steve> To unsubscribe from the emacspeak list or change your
    Steve> address on the emacspeak list send mail to
    Steve> "emacspeak-request@xxxxxxxxxxx" with a subject of
    Steve> "unsubscribe" or "help".



|All Past Years |Current Year|


If you have questions about this archive or had problems using it, please contact us.

Contact Info Page