On Mon, Jun 05, 2006 at 17:55:55 +0200,
Jens Seidel <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 05, 2006 at 10:33:28AM -0500, Bruno Wolff III wrote:
> > > > I also uninstall stuff before doing the update.
> > >
> > > Right. A better way is to create a (RPM or .deb) package. Nevertheless
> > > there
On Mon, Jun 05, 2006 at 10:33:28AM -0500, Bruno Wolff III wrote:
> > > I also uninstall stuff before doing the update.
> >
> > Right. A better way is to create a (RPM or .deb) package. Nevertheless
> > there is no debian/ directory in Wesnoth and the official one in the
> > Debian package may be o
> > I also uninstall stuff before doing the update.
>
> Right. A better way is to create a (RPM or .deb) package. Nevertheless
> there is no debian/ directory in Wesnoth and the official one in the
> Debian package may be outdated. I read short time ago in the Debian
> Weekly News that not shippin
On Fri, Jun 02, 2006 at 02:08:52PM -0500, Bruno Wolff III wrote:
> On Fri, Jun 02, 2006 at 20:53:50 +0200,
> Daniel Bruegmann <[EMAIL PROTECTED]> wrote:
> >
> > Before running make, I ran make clean. In INSTALL I read that I should
> > run make maintainer-clean (by the way, INSTALL refers to CV
Hiho everyone!
I just wanted to say that we are, looking at the schedule at
http://www.wesnoth.org/wiki/Wesnoth1.2ReleasePlan, now meant to be in
the state a feature freeze and a soft string freeze. I would suggest
that we do release a 1.1.5 and afterwards there is bug fixing only. No
new stri
