public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marcelo Fontenele S Santos <msantos@pobox.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Misc questions on ebuilds
Date: Sun, 16 Jun 2002 15:40:49 -0300	[thread overview]
Message-ID: <200206161541.04319.msantos@pobox.com> (raw)
In-Reply-To: <20020614225629.A19382@lostlogicx.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 15 June 2002 00:56, Brandon Low wrote:
> Have you used the "lintool" script that comes with gentoolkit?  It is a
> nice tool which checks for most common ebuilding mistakes...
>
> On Fri, 06/14/02 at 22:21:59 -0500, Keith Gross wrote:
> > I'm trying to improve the ebuilds I've been writing by reviewing the
> > existing ebuilds but there seems they very widely.  Everything from
> > simple somewhat crude examples that looksomething like my efforts to
> > other that are much larger and elaborate.

Hi,

I have some questions about lintool.

In the lintool man page it says that it checks for conformance with the ebuild 
style guide. I found a Gentoo Linux Developers HOWTO and the Eclass (OOP-like 
ebuild) HOWTO but no Style Guide. Where is it?

I also don't know what those errors mean:
- - Testing for malformed headers
- - Testing for presence of env vars

What is a malformed header? 
Or a wellformed? 
Is the one in skel.ebuild correct?

What is the error in using an env var inside an ebuild? 
How can/can't one be used?

If you run lintool on skel.ebuild it gives:

/usr/portage/skel.ebuild                                               : Not 
OK

- -------------------------------------------------------------------------------
 Summary for all 1 ebuild(s) checked                             # 
errors/warns
- -------------------------------------------------------------------------------
Testing for illegal space characters, weird backslash formatting  : 0 / 0
Testing for malformed headers                                     : 0 / 1
Testing for occurence of deprecated try                           : 0 / 0
Testing for superfluous A=${P}.tar.gz                             : 0 / 0
Testing for empty DEPEND                                          : 0 / 1
Testing for empty HOMEPAGE                                        : 0 / 0
Testing for empty DESCRIPTION                                     : 0 / 0
Testing for presence of env vars                                  : 1 / 1
Testing for sane USE flag usage                                   : 0 / 0

Total number of ebuilds with errors                               : 1 (100%)
Total number of ebuilds with warnings                             : 1 (100%)

Thanks,
- -- 
Marcelo Fontenele S Santos<msantos@pobox.com>

ICQ# 2103731
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9DNu0CBYGr8x5oV8RAl54AJ0RIoZIWwewBsUcd1h62Hjge3PrewCdHitS
7+TW6Yw1t0X8G0X2r+uffeA=
=CcxG
-----END PGP SIGNATURE-----



      parent reply	other threads:[~2002-06-16 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15  3:21 [gentoo-dev] Misc questions on ebuilds Keith Gross
2002-06-15  3:56 ` Brandon Low
2002-06-15 19:53   ` [gentoo-dev] " Mark Gordon
2002-06-16  6:12     ` Brandon Low
2002-06-16 18:40   ` Marcelo Fontenele S Santos [this message]

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=200206161541.04319.msantos@pobox.com \
    --to=msantos@pobox.com \
    --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