public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Some 'proper coding' notes for ebuilds
Date: Sun, 3 Aug 2003 15:15:55 -0700	[thread overview]
Message-ID: <200308031515.55688.george@gentoo.org> (raw)
In-Reply-To: <200308032135.01978.stuart@gentoo.org>

On Sunday 03 August 2003 13:34, Stuart Herbert wrote:
> On Sunday 03 August 2003 9:27 pm, George Shapovalov wrote:
> As a new developer, I've been told repeatedly that lintool is not worth
> using. Heck, it even says that in the Ebuild howto on the website, iirc.
and
>Warning: Be warned - lintool is very broken. Use repoman instead.

Sure, don't use lintool *instead* of repoman (just trying to clarify so that 
nobody will take my words out of context (Stuart: not directed at you 
personally, as I am sure you understood what I meant ;))). However I still 
find lintool quite usefull for a basic ebuild composition checks, it seems to 
catch a bit more of those. 

I would say use both, with repoman taking precedence where they contradict 
(although I never saw this happen). I usually run ebuilds through lintool 
first (you *will* get few false errors/warnings, so you need to know the tool 
and the policy :)) and when everything ready run repoman on a dir..
Although clearly use of lintool *is not required* anymore..

George



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-03 22:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  2:29 [gentoo-dev] Some 'proper coding' notes for ebuilds Mike Frysinger
2003-08-03  2:34 ` Mike Frysinger
2003-08-03  2:38   ` Mike Frysinger
2003-08-03  2:50     ` Kumba
2003-08-03  3:04       ` Mike Frysinger
2003-08-03 15:23         ` Martin Schlemmer
2003-08-03 18:44           ` Mike Frysinger
2003-08-03 15:10     ` Mamoru KOMACHI
2003-08-03 15:40       ` Paul de Vrieze
2003-08-03 16:23         ` Mamoru KOMACHI
2003-08-03 16:27       ` Georgi Georgiev
2003-08-03 17:04         ` Mamoru KOMACHI
2003-08-03 15:30     ` Martin Schlemmer
2003-08-11 13:45     ` Patrick Kursawe
2003-08-11 14:58       ` Mike Frysinger
2003-08-03  5:31   ` Jason A. Mobarak
2003-08-03  4:56     ` Mike Frysinger
2003-08-03  6:11     ` Luke-Jr
2003-08-03 14:55   ` Stuart Herbert
2003-08-03 15:18     ` Martin Schlemmer
2003-08-03 18:07       ` Stuart Herbert
2003-08-03 18:48         ` Mike Frysinger
2003-08-03 18:53           ` Stuart Herbert
2003-08-03 20:27             ` George Shapovalov
2003-08-03 20:34               ` Stuart Herbert
2003-08-03 22:15                 ` George Shapovalov [this message]
2003-08-03 22:56                   ` Don Seiler
2003-08-08 15:21                     ` Anthony de Boer
2003-08-08 15:33                       ` Marius Mauch
2003-08-08 18:25                       ` George Shapovalov
2003-08-08 19:16                         ` Douglas Russell
2003-08-08 20:12                           ` George Shapovalov
2003-08-08 23:01                             ` Mike Frysinger
2003-08-10  2:58                             ` George Shapovalov
2003-08-03 22:19                 ` Aron Griffis
     [not found]             ` <20030803223541.05d10e90.spider@gentoo.org>
2003-08-03 20:43               ` Stuart Herbert

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=200308031515.55688.george@gentoo.org \
    --to=george@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