gnewsense-dev
[Top][All Lists]
Advanced

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

Re: [Gnewsense-dev] GNU Emacs and GFDL documentation.


From: Sam Geeraerts
Subject: Re: [Gnewsense-dev] GNU Emacs and GFDL documentation.
Date: Wed, 26 Dec 2012 10:56:14 +0100

Op Tue, 25 Dec 2012 13:43:21 +0100
schreef Marek Buras <address@hidden>:

> Looks like GNU Emacs (23.2) in Parkes has been stripped from GFDL
> documentation and there are no additional packages available
> providing removed files. So I decided to modify existing packages and
> restore missing documentation. My approach isn't perfect (patch is
> ca. 14MB), but at least I can access info files. Modified dsc and
> dpkg related stuff can be obtained here:
> http://cyfr0n.c0.pl/gns/parkes/emacs23_23.2+1-7gnewsense1.dsc
> http://cyfr0n.c0.pl/gns/parkes/emacs23_23.2+1-7gnewsense1.debian.tar.gz
> The original sources can be downloaded with apt-get source (I haven't
> touched *orig.tar.gz). Does this approach meet gNewSense policies for
> packages? If not, what could be done to restore documentation for
> Emacs in gNewSense?

My plan is to import GFDL packages from Debian non-free. That should be
a lot less work than merging docs into the main packages.

> Moreover I looked at 24.2 package for Debian wheezy (made by Rob
> Browning) and it looks like not that hard task to port it to
> gNewSense (there will be some implications probably, such as
> rebuilding auctex and maybe other elisp stuff). If you are interested
> in having modern Emacs in base I can work on that.

I did a quick search and only found it in Sid. I learned from our work
on Metad that backporting gets messy very quickly. What seems at first
like an innocent package with few dependencies to be resolved often
turns out needing a whole chain of binary and build dependencies,
potentially all the way down to libc. Is there a compelling reason to
have Emacs 24.2 in Parkes?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]