public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo alt-projects meeting 9/26 1900 UTC
Date: Fri, 16 Sep 2005 11:06:29 +0200	[thread overview]
Message-ID: <200509161106.37324@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <432A0A28.4080308@ieee.org>

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

On Friday 16 September 2005 01:56, Nathan L. Adams wrote:
> I'm writing a tool, called esyntaxer, that finds certain common ebuild
> errors and automagically corrects them if possible. Yes, I'm aware of
> the overlaps with repoman, and no this isn't a duplication of work.
Actually, I already have prepared a ruby script that I use to find violators 
to the syntax (like enewuser with /bin/false and cp called with extra 
options). It's on http://dev.gentoo.org/~flameeyes/ruby-checker.tbz2 .
It's not complete, but it works when it comes to checking for these simple 
cases.

I don't trust automatic correction, false positives can always happen, 
currently my way to proceed with such problems is opening a big bug and 
poking maintainers to fix them :)

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)

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

  reply	other threads:[~2005-09-16  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 23:30 [gentoo-dev] Gentoo alt-projects meeting 9/26 1900 UTC Kito
2005-09-15 23:56 ` Nathan L. Adams
2005-09-16  9:06   ` Diego 'Flameeyes' Pettenò [this message]
2005-09-16 23:36     ` Nathan L. Adams
2005-09-16  4:22 ` Kito
2005-09-16 10:03 ` Diego 'Flameeyes' Pettenò
2005-09-16 16:39 ` [gentoo-dev] " Kito

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=200509161106.37324@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@gentoo.org \
    --cc=gentoo-dev@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