update of jed-extra

[G. Milde]

On  3.07.05, Jörg Sommer wrote:
> G. Milde schrieb am Fri 01. Jul, 17:07 (+0200):
> > On 30.06.05, Jörg Sommer wrote:

> > I just updated http://jedmodes.sourceforge.net/cvs/jedmdoes.tgz and
> > did a new "release" of the files from the Jedmodes CVS repository.
> > Quite a lot of the files by Paul Boekholt are now no longer in the CVS
> > and must be fetched separately.  
> 
> Why is? What's the reason?

The main reason is that the original concept of doing all the work in the
webspace and neglect Sourceforges release system as well as CVS led to the
closing of Jedmodes (due to preceived inactivity).

We applied for reopening, I moved the sources to CVS and did a "pro forma"
release of a CVS snapshot.

Paul decided this way mainly because of problems with CVS. There were some
instabilities with Sourceforge CVS access. Also, the ViewCVS tool for http
browsing/download only allows downloads of single files. So, for
multi-file-modes, Paul instead did "release packages".
 
> > > firstly I must say the provided files of jedmodes.sf.net are dirty!
> > 
> > What do you mean with provided files? jedmodes.sf. is quite heterogen, with
> > files provided by several different developers. The primary inteded use
> > is browsing the site and downloading individual modes.
> 
> But that's not the intent of the Debian package.

I know, but the the Debian package should not just download and pack the
complete cvs snapshot. 

(As well as tetex-extra doesnot pack the complete CTAN. Of course,
Jedmodes is smaller. But as CTAN, it is not a "package" or "product" but
a "repository" or "archive" with internal inconsistencies and
redundancy.)

I think we need a new reflection on what jed-extra should provide and
what not.

 
> > > No makefile, 
> > What kind of makefile should this be?
> make install would help much

Again, it would not make sense to install all of Jedmodes.

The recommended (by me) method is:

 * Place the mode and requirements in Jed_Home_Libray or Jed_Site_Library
 * Run update_ini (from make_ini.sl) on the library to preparse and create
   autoloads and online documentation.
 * Read the mode to find usage instructions, set custom variables, etc.
   
 
> > > no copyright notice (this might cause trouble with Debian)
> > 
> > There is a copyright notice on the site, as well as in most of the
> > individual files (except rather old ones).
> 
> Can you add a COPYING file to the tar.gz?

Should this be a full copy of the GPL or would a small pointer with URL
suffice.

 
> > > I have some problems/questions:
> > > 
> > > * should apsmode/apsconf/SLang.ssh go to /usr/share/a2ps/sheets/? Is it
> > >   the same like a2ps/slang.ssh?
> > 
> > apsmode and a2ps are distinct modes (by different developers) that
> > happen to do similar things. Please do not confuse.
> 
> Oh. I didn't recognize this. What do you think? Should we use SLang.ssh
> as Rafael suggested?

Actually, I think we should drop either apsmode or a2ps. As I do not use
either of both, maybe Paul can say something about this.

> > > * why does the old version of 05home-lib.sl take care of site-lib?
> > 
> > home-lib.sl initializes both, home-lib and site-lib. The name is for
> > historical reasons, as Jed_Site_Library (and Jed_Local_Library) where
> > added later.
> 
> Why? Why to care about site-lib? 

Because caring about the libraries for jed extensions is what home-lib.sl
was written for. Also non-Debian administrators might want to add
extensions for all users of their site/machine.

> There is not reference in jed (upstream)

Of course not, as jed (unfortunately) doesnot care about extensions on a
higher level than providing set_jed_library_path and Jed_Doc_Files and
Color_Scheme_Path and Jed_Highlight_Cache_Dir and ... to be used in
.jedrc or jed.conf.

home-lib.sl takes care of these "hooks" and provides a simple basic
setup of the extension libraries. Think of this as a kind of "bootstrap"
to facilitate the use of all Jedmodes modes as well as other modes
homebrewn or downloaded from elsewhere. 

(This is why I want it to be in jed-common: it is usefull without all the
rest of jed-extra for both, the end user adding or modifying a mode as
well as other Debian packages providing a jed mode.)

> or jedmodes (exclude home-lib) on Jed_Site_Library?

Maybe I should ask a "generic usage documentation" for Jedmodes (under
/doc/ as well as in the README of the "release".


Günter


-- 
G.Milde web.de