public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wesnoth version
Date: Sat, 5 May 2007 09:04:19 -0500	[thread overview]
Message-ID: <200705050904.19325.bss03@volumehost.net> (raw)
In-Reply-To: <9238e8de0705050640o3de68d0ub4bd8184d05b9a74@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

On Saturday 05 May 2007, "Marko Kocić" <marko.kocic@gmail.com> wrote 
about '[gentoo-user] Wesnoth version':
> Is there a specific reason why gentoo doesn't provide development
> versions of Battle for Wesnoth (games-strategy/wesnoth)?
>
> I couldn't find anything in bug database. Development versions (1.3.2)
> are pretty stable, so I can't see a reason why are not included in
> "~x86". As for "x86", 1.2.4 (latest stable) seems ok.
>
> Should I open a bug for that?

Yeah, a new numbered release deserves it's own ebuild, even if it has to 
linger in package.mask.  Make sure it's been 2-3 days after the release 
and then file a version bump bug.  Please report if "simply renaming" the 
existing ebuild works and/or what you had to change to get a clean 
compile/install.

If you follow Wesnoth closely, but aren't part of upstream, you might 
consider becoming a/the gentoo package maintainer for it.  IIRC, IMHO, the 
packaging for Wesnoth could use a little "love".

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-05 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 13:40 [gentoo-user] Wesnoth version Marko Kocić
2007-05-05 14:04 ` Boyd Stephen Smith Jr. [this message]
2007-05-05 18:00   ` Marko Kocić
2007-05-06 20:06     ` Boyd Stephen Smith Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200705050904.19325.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox