vm team mailing list archive

[Jonathan Underwood <612222@xxxxxxxxxxxxxxxxxx>]

On 11 August 2010 14:38, Uday Reddy <u.s.reddy@xxxxxxxxxxxxx> wrote:
> Uday S Reddy writes:
>
>> There were also the documentations of other non-gnu packages in
>> /usr/share/doc, such as AucTeX, psgml etc.  So, it looks like gnu and
>> non-gnu packages are treated differently.
>
> Our CentOS installation has a directory /usr/share/emacs/site-lisp,
> and the various packages like Emacsspeak, AucTeX and psgml use this
> for everything, including images, data, documentation etc.
>
> Does anybody else use this structure?

This is the structure we use for emacs add-on packages for Fedora etc
simply because that's how things have been for a long time, and this
is simply because upstream emacs only creates
/usr/share/emacs/site-lisp by default, and hasn't given any
consideration to how packages should structure themselves. Over time,
packages have become more complex, adding images etc as well as lisp.
To reiterate: this situation (i.e. dumping everything under site-lisp)
is sub-optimal, and needs reconsidering. But it needs to be done in
consultation with upstream emacs devs, so that it becomes a standard
adopted by all add-on packages, not just something VM decides upon.
And it needs to be standardized across distributions too. FWIW, xemacs
has a much better structure for packages:

$ ls /usr/share/xemacs/xemacs-packages/
etc/     lib-src/ lisp/    man/     pkginfo/

[That's for the packages which are packaged up by xemacs devs]

-- 
Wishlist: Install NEWS in builds
https://bugs.launchpad.net/bugs/612222
You received this bug notification because you are a member of VM
development team, which is a direct subscriber.

Status in VM (View Mail) for Emacs: Triaged

Bug description:
The VM NEWS file gets lost when distros install VM.  Change the build process so that it gets installed in emacs/etc.  

Ulrich thinks all VM-related files should go into a subdirectory $(prefix)/share/emacs/etc/vm.  Other files that could go into this subdirectory are 

CHANGES
README
TODO

Perhaps the images files should go here too?