Edit detail for AndrewBurrow revision 1 of 1

1
Editor: 192.168.1.21
Time: 2003/04/15 11:58:34 GMT+0
Note: Example of external editor and lynx

changed:
-
I was going to use this homepage to journal some of my work, but I now
host this information on my own Zwiki at
http://zwiki.sial.rmit.edu.au/albCorpus/


Emacs: Is It More of a Distraction Than Its Worth

  The ExternalEditor now works well enough for me.  The clincher was
  realising that the header field 'Log:' requires trailing whitespace.
  So I have turned off the lovely whitespace-mode in emacs.

  I also use 'lynx(1)' to call an external editor from a text field by
  pressing C-e C-e.  The following works for me::

    lynx -editor=emacs http://zwiki.org/AndrewBurrow

  This is actually quite useful when you are restricted to a console.


Tracking ZWiki Sources Using CVS

  Per TheCederqvist I am going to use CVS to track the ZWiki sources.
  This is a good compromise to getting developer access to the CVS
  because, I can use my own CVS repository for my own changes, and
  always submit them later as diffs.

  To do this I took two steps:

  * Extract a tarball of the ZWiki source [1].  Example::

      tar --extract --gzip --file ZWiki-0.15.0.tgz

  * Import the source into the CVS repository as a vendor branch.  Use
    the '-ko' option to leave the original ZWiki CVS keywords in place.
    Example::

      cd ZWiki
      cvs import -ko -m "Import of ZWiki 0.15" Zope/ZWiki zwiki_org release_0_15_0

  Note that CVS places the imported ZWiki source into its own branch.
  See TheCederqvist for more information.


Installing ZWiki From Own CVS Repository --- Mon, 03 Feb 2003 16:15:41 +1100

  Having removed the 'zope-zwiki' package from my box, I want to install
  the ZWiki source from my own CVS repository.

  The first step is to change the permissions on the product directory
  to give myself write access.  I decide to do this via a *zopista*
  group.  Namely, as root::

    addgroup zopista
    adduser andrew zopista
    chown root.zopista /usr/lib/zope/lib/python/Products
    chmod g+ws /usr/lib/zope/lib/python/Products

  Unfortunately, one has to log out and back in so that the new group
  membership is known to the system.

  The next step is to install the ZWiki source from my own CVS
  repository.  Namely::

    cd /usr/lib/zope/lib/python/Products/
    cvs checkout -d ZWiki Zope/ZWiki

  Then I have to restart Zope and Apache, because I access Zope through
  Apache pcgi.  Before this can become a routine there are some more
  steps to increase my access without needing to go superuser every 5
  minutes.  Namely, I edit 'sudoers(5)', so that the steps I need look
  like this (though I know there are better solutions out there)::

    sudo /etc/init.d/zope restart
    sudo /etc/init.d/apache restart

<hr>


I was going to use this homepage to journal some of my work, but I now host this information on my own Zwiki at http://zwiki.sial.rmit.edu.au/albCorpus/

Emacs: Is It More of a Distraction Than Its Worth

The ExternalEditor now works well enough for me. The clincher was realising that the header field Log: requires trailing whitespace. So I have turned off the lovely whitespace-mode in emacs.

I also use lynx(1) to call an external editor from a text field by pressing C-e C-e. The following works for me:

    lynx -editor=emacs http://zwiki.org/AndrewBurrow

This is actually quite useful when you are restricted to a console.

Tracking ZWiki Sources Using CVS

Per TheCederqvist I am going to use CVS to track the ZWiki sources. This is a good compromise to getting developer access to the CVS because, I can use my own CVS repository for my own changes, and always submit them later as diffs.

To do this I took two steps:

  • Extract a tarball of the ZWiki source [1]?. Example:
          tar --extract --gzip --file ZWiki-0.15.0.tgz
    
  • Import the source into the CVS repository as a vendor branch. Use the -ko option to leave the original ZWiki CVS keywords in place. Example:
          cd ZWiki
          cvs import -ko -m "Import of ZWiki 0.15" Zope/ZWiki zwiki_org release_0_15_0
    

Note that CVS places the imported ZWiki source into its own branch. See TheCederqvist for more information.

Installing ZWiki From Own CVS Repository --- Mon, 03 Feb 2003 16:15:41 +1100

Having removed the zope-zwiki package from my box, I want to install the ZWiki source from my own CVS repository.

The first step is to change the permissions on the product directory to give myself write access. I decide to do this via a zopista group. Namely, as root:

    addgroup zopista
    adduser andrew zopista
    chown root.zopista /usr/lib/zope/lib/python/Products
    chmod g+ws /usr/lib/zope/lib/python/Products

Unfortunately, one has to log out and back in so that the new group membership is known to the system.

The next step is to install the ZWiki source from my own CVS repository. Namely:

    cd /usr/lib/zope/lib/python/Products/
    cvs checkout -d ZWiki Zope/ZWiki

Then I have to restart Zope and Apache, because I access Zope through Apache pcgi. Before this can become a routine there are some more steps to increase my access without needing to go superuser every 5 minutes. Namely, I edit sudoers(5), so that the steps I need look like this (though I know there are better solutions out there):

    sudo /etc/init.d/zope restart
    sudo /etc/init.d/apache restart


subtopics: