public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Error compiling sawfish-20020611.ebuild
Date: Mon, 17 Jun 2002 20:16:19 +0200	[thread overview]
Message-ID: <20020617201619.3cef5994.spider@gentoo.org> (raw)
In-Reply-To: <1024333489.24873.4.camel@orcana>

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

begin  quote
On 17 Jun 2002 13:04:47 -0400
Richard Reich <rreich@rdrtech.com> wrote:

> Here is the error, is there anything I can do to fix this?
> 
> Thanks 
> Richard Reich

1) Read ChangeLog.  Its been a documented fact that Sawfish snapshots
are broken and fail to compile for quite some time now.  
2) http://bugs.gentoo.org/ Has at least two exactly the same entries. 

3) its also been in the forums.

4) its been in my private mails too.

5) file bugs upstream or Fix it. the only reason its still there, is
because the noise of it being broken is less than the noise I recieved
when I stubbornly declined to include it because it was just that...
broken.

Sorry to appear irritated, but I am, I've been facing broken snapshots
since april, and so far I've gotten no solid documentation on what makes
it build, and quite some pointers that "but they have it".  


Yours, 
  Irritable Maintainer.  

aka. Spider




--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-06-17 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 17:04 [gentoo-dev] Error compiling sawfish-20020611.ebuild Richard Reich
2002-06-17 18:16 ` Spider [this message]
2002-06-17 18:34   ` Richard Reich

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=20020617201619.3cef5994.spider@gentoo.org \
    --to=spider@gentoo.org \
    --cc=gentoo-dev@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