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: Fri, 8 Aug 2003 11:25:50 -0700	[thread overview]
Message-ID: <200308081125.50278.george@gentoo.org> (raw)
In-Reply-To: <20030808112101.C24644@leftmind.net>

On Friday 08 August 2003 08:21, Anthony de Boer wrote:
> Don Seiler wrote:
> > Can repoman not be updated to catch what only lintool catches now, so
> > that we can have our all-in-one kwik-e-tool?
> The implication I see in the documentation is that repoman is for Gentoo
> developers only[0], and implies you need CVS access to the Gentoo tree,
> while one shouldn't bother with lintool at all[1].  As a non-dev wanting
> to submit the occasional ebuild, I'd like a tool I can use to make sure
> I don't miss anything obvious that a CVS committer would see when he/she
> runs repoman against my ebuild.

I would like to second that. Even as a developer I like to do two passes - 
first is done with lintool, while I tweak an ebuild in my "live" tree (and I 
do have them separate, - gives me quite a bit of flexibility in tweaking 
without a risk of inadvertedly committing some local changes to the global 
tree) and then using repoman to finalize all "distributed" stuff, like 
digests, etc. in the cvs tree. Nothing beats lintool (so far and if you know 
your way around it) for the first checks that involve the ebuild itself..

George



--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-08-08 18:26 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
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 [this message]
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=200308081125.50278.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