Emacspeak discussion list

["T.V Raman" <raman AT google.com>]

No problems, glad we each learnt something useful from this:-)



Robert Melton writes:
 > TV--
 > 
 > Agreed, from now on I will direct discussions off of here if they pop up.  
 > Additionally, I have updated my README.md to make it clear they should 
 > only use it if they are developers and can puzzle out any issues.
 > 
 > Sorry for the additional noise on the list.  Will ensure from here on out 
 > anything here will be referencing the version committed to emacspeak. 
 > 
 > > On Jan 9, 2024, at 22:14, T.V Raman (via emacspeak Mailing List) 
 > > <emacspeak AT emacspeak.net> wrote:
 > > 
 > > Thanks for the clarification Tim!
 > > 
 > > Robert, if Tim is   correct, could you make sure that folks using and
 > > reporting issues on your bleeding edge swiftmac from your git repo
 > > dont send their messages to the emacspeak list?
 > > 
 > > 1. It's not useful since at least I for one have  no clue at that
 > >   point about what they are saying
 > > 2. It's a distraction now, and potentially confusing a year from now
 > >   when users perform web search and run into these out-of-context 
 > > threads.
 > > 
 > > "Tim Cross" (via emacspeak Mailing List) writes:
 > >> 
 > >> Agree. Only mentioned the use of the environment variable in the context
 > >> of installing the most recent swiftmac server from Robert's own github
 > >> rather than the one actually in the emacspeak tree itself. My
 > >> understanding (which could easily be wrong) was that the issue was with
 > >> getting a copy from RObert's private git repo and having that installed
 > >> inside the Emacspeak install, replacing the version included in
 > >> emacspeak.
 > >> 
 > >> Of course, this also has other issues not yet discussed. For example,
 > >> when someone has installed from Robert's private repo and copied the
 > >> server into the emacspeak tree, then enxt time the user goes to pull
 > >> from the emacspeak repo, git will tell them they need to either commit
 > >> or stash their changes. THis will likely cause all sorts of problems for
 > >> users as committing will mean their local emacspeak copy has diverged
 > >> from the main emacspeak repo.
 > >> 
 > >> I do wonder if there is a better way of doing this. For example, I think
 > >> it might be possible for emacspeak to include Robert's swiftmac
 > >> repository as a sub repository within the emacspeak repository. When
 > >> people do a checkout of the emacspeak repository, they would get that
 > >> repository as well, but as it is actually its own repository, they could
 > >> also switch its branch, lets say to the development branch. This would
 > >> avoid all the current issues and allow those who want to to run Robert's
 > >> bleeding edge development version while others just stick with the
 > >> stable version, plus Robert wouldn't need to do pushes from his repo
 > >> into the emacspeak repo. However, I've only read about using this
 > >> sub-repo spproach and don't know what the hidden complexities/issues are
 > >> or what other limitations this could introduce. 
 > >> 
 > >> Date: Wed, 10 Jan 2024 10:38:43 +1100
 > >> 
 > >> ----------------------------------------------------------------------
 > >> Emacspeak discussion list -- emacspeak AT emacspeak.net
 > >> To unsubscribe send email to:
 > >> emacspeak-request AT emacspeak.net with a subject of: unsubscribe
 > > 
 > > -- 
 > > Emacspeak discussion list -- emacspeak AT emacspeak.net
 > > To unsubscribe send email to:
 > > emacspeak-request AT emacspeak.net with a subject of: unsubscribe

--