Gentoo Archives: gentoo-dev

From: George Shapovalov <george@g.o>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] Some 'proper coding' notes for ebuilds
Date: Fri, 08 Aug 2003 20:12:34
Message-Id: 200308081312.16205.george@gentoo.org
In Reply to: Re: [gentoo-dev] Some 'proper coding' notes for ebuilds by Douglas Russell
1 On Friday 08 August 2003 12:16, Douglas Russell wrote:
2 > I've been looking into integrating the lintool functionality into repoman
3 > for the last couple of days, am beginning to make some headway. I will let
4 > you know where I've got something worth looking at.
5 >
6 > I'm aware that lintool is "broken", but nobody seems to know exactly what
7 > is wrong with it. This would help enoumously if someone could enlighten
8 > me...
9
10 It isn't actually broken that much. This is the one I am getting every time:
11 * Testing for malformed headers : failed
12 - (W) Has illegal or suspect headers:
13 - (E) Missing Copyright statement
14
15 This is due to 2003 not being in the list of "valid years".
16
17 The main reason why lintool is deprecated is that it only performs
18 ebuild-specific checks, i.e. no digest checking or, perheaps the main
19 problem, no dependency checking, like repoman does. The deprecation was
20 really put to force everybody use repoman from what I remember. Although I
21 would appreciate having an *additional* ebuild-specific tool - I find it
22 useful to have the ability to do easy preliminary checks on submitted stuff..
23 (that is to say, I would personally appreciate having lintool around if
24 possible, just make sure everybody understands that *this is not a
25 substitute* for repoman!). But having lintool checks incorporated in repoman
26 is definitely usefull for those who do not want to bother with multiple
27 tools..
28
29 George
30
31
32
33 --
34 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Some 'proper coding' notes for ebuilds Mike Frysinger <vapier@g.o>
Re: [gentoo-dev] Some 'proper coding' notes for ebuilds George Shapovalov <george@g.o>