Date: Tue, 30 Mar 1999 16:45:44 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Stromberg <eplmst AT lu DOT erisoft DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: Directions on how to create a DJGPP package of a port
In-Reply-To: <199903301410.QAA02324@juno.erisoft.se>
Message-ID: <Pine.SUN.3.91.990330163920.6660C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 30 Mar 1999, Martin Stromberg wrote:

> During the problems I had with emacs crashing (after C-w-ing a big
> buffer) I offered to send my newly built emacs to Eli. He said thanks
> for the offer but making a DJGPP package of emacs involved more
> efforts (possibly time-consuming things?) than creating the binary
> it-self.

The source distribution needs to be updated as well, and I usually test 
that the changed sources build on all platforms (LFN and non-LFN) that I 
can access.

In the case you cite, there was also a question of other bug-fixes that 
were done since 19.34 was released (why only fix the single bug that you 
reported, and not the others?), which is a lot of mundane and error-prone 
work.  In addition, I don't like uploading a binary which I don't use 
actively, since I cannot guarantee its quality.

> Now I wonder if there is a guide somewhere that explains the steps of
> making a DJGPP package?

There is none.  You are supposed to do whetever it takes to make the zip 
files build correctly on every supported platform, and to write some kind 
of README file which explains any DJGPP-specific points.