From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org
X-Spam-Level: **
X-Spam-Status: No, score=2.4 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE,
	INVALID_DATE,MAILING_LIST_MULTI,RDNS_NONE autolearn=no
	autolearn_force=no version=4.0.0
Received: from [62.67.120.43] (helo=columbus.localdomain)
	by cvs.gentoo.org with esmtp (Exim 3.30 #1)
	id 162ac6-0007GU-00
	for gentoo-dev@cvs.gentoo.org; Sat, 10 Nov 2001 09:04:11 -0700
Received: by columbus.localdomain (Postfix, from userid 501)
	id D1A7D203D6; Sat, 10 Nov 2001 17:03:30 +0100 (CET)
To: gentoo-dev@cvs.gentoo.org
References: <1005392055.10442.2.camel@zoidberg>
	<20011110165601.1b5869a1.karltk@prosalg.no>
	<1005406570.28610.0.camel@zoidberg>
X-Attribution: AV
From: Andreas Voegele <voegelas@users.sourceforge.net>
In-Reply-To: <1005406570.28610.0.camel@zoidberg>
Message-ID: <m2bsiahaum.fsf@columbus.localdomain>
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [gentoo-dev] Re: All Developers!
Sender: gentoo-dev-admin@cvs.gentoo.org
Errors-To: gentoo-dev-admin@cvs.gentoo.org
X-BeenThere: gentoo-dev@cvs.gentoo.org
X-Mailman-Version: 2.0
Precedence: bulk
Reply-To: gentoo-dev@cvs.gentoo.org
List-Help: <mailto:gentoo-dev-request@cvs.gentoo.org?subject=help>
List-Post: <mailto:gentoo-dev@cvs.gentoo.org>
List-Subscribe: <http://cvs.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@cvs.gentoo.org?subject=subscribe>
List-Id: Gentoo Linux development list <gentoo-dev.cvs.gentoo.org>
List-Unsubscribe: <http://cvs.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@cvs.gentoo.org?subject=unsubscribe>
List-Archive: <http://cvs.gentoo.org/pipermail/gentoo-dev/>
Date: Sat Nov 10 09:05:02 2001
X-Original-Date: 10 Nov 2001 17:03:29 +0100
X-Archives-Salt: f2ea3aba-587e-45de-bbfb-746709a4db47
X-Archives-Hash: cb987a2ff0d5c655e350d3e23046f9f7

Mikael Hallendal writes:

> We should write some spec. on how ebuilds should look like
> (guidelines for style) and then make a emacs and a vi mode for
> editing ebuilds that controls the style.

If only tabs and *no* spaces were allowed at the beginning of lines it
would be very easy to check ebuild scripts for wrong spaces.

We could rip the required code from the Emacs Makefile mode, which
checks for suspicious tabs and highlights these areas when a user
tries to save the Makefile.

BTW, if a single tab was used in front of dependencies the output
would look like this:

tabwidth 4:

DEPEND="virtual/glibc
    virtual/x11
RDEPEND="virtual/glibc
    virtual/x11

tabwidth 8:

DEPEND="virtual/glibc
        virtual/x11
RDEPEND="virtual/glibc
        virtual/x11

IMHO both outputs look good, and with this solution developers could
still set the tabwidth to 4 or 8.

-- 
Andreas