public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Re: All Developers!
Date: Sat Nov 10 06:17:01 2001	[thread overview]
Message-ID: <1005398351.3250.6.camel@nosferatu.lan> (raw)
In-Reply-To: <m2bsiasrxw.fsf@columbus.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

On Sat, 2001-11-10 at 14:58, Andreas Voegele wrote:
> Martin Schlemmer writes:
> 
Hi

> > On Sat, 2001-11-10 at 13:34, Mikael Hallendal wrote:
> > 
> > > I'm currently fixing lots of ebuilds but it's hard work.
> >
> > also remember to convert to tabs!
> 
> DEPEND="virtual/glibc
>         >=sys-libs/db-3.2
> ^^^^^^^^
> 
> Do you put spaces or a single tab in front of dependencies?
> 
a single tab.

> I prefer 8 spaces since I've set the tabwidth to 4.  But if everbody
> else uses a tab I'll use a tab too.
> 
then i guess you will have to start using a tabwidth of 4, or live with
it, as it is the wish of drobbins :)

> I don't like the combination of tabs and spaces in RDEPEND very much
> though.  If the tabwidth is set to 4 the output looks like this:
> 
> DEPEND="virtual/glibc
>     virtual/x11
> RDEPEND="virtual/glibc
>      virtual/x11
> 
> There are 4 "spaces" at the beginning of the second line and 5
> "spaces" in the fourth line.
> 
> IMHO either a single tab should be used in both cases or 8 spaces
> should be used in the first case and 9 spaces in the second case.
> 
> On the other hand, there are more important things than the number of
> tabs and spaces in front of dependencies :-)
> 
true, but we need consistancy.

> -- 
> Andreas

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-11-10 13:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-10  4:35 [gentoo-dev] All Developers! Mikael Hallendal
2001-11-10  5:22 ` Martin Schlemmer
2001-11-10  6:00   ` [gentoo-dev] " Andreas Voegele
2001-11-10  6:12     ` Mikael Hallendal
2001-11-10  6:17     ` Martin Schlemmer [this message]
2001-11-10  7:58 ` [gentoo-dev] " Karl Trygve Kalleberg
2001-11-10  8:37   ` Mikael Hallendal
2001-11-10  9:05     ` [gentoo-dev] " Andreas Voegele
2001-11-10  9:29       ` Martin Schlemmer
2001-11-10  9:38       ` Chad Huneycutt
2001-11-10 11:25         ` Daniel Robbins
2001-11-10 13:42           ` Chris Houser
2001-11-10 14:05             ` Daniel Robbins
2001-11-10 14:23               ` Aron Griffis
2001-11-11  6:27               ` Mikael Hallendal
2001-11-11  6:35                 ` Martin Schlemmer
2001-11-11  6:41                   ` Mikael Hallendal
2001-11-21 19:16                   ` Damon M. Conway
2001-11-21 20:08                     ` Daniel Robbins
2001-11-11 10:06                 ` Andreas Voegele
2001-11-11 12:09                   ` jano
2001-11-11 14:17                     ` Mikael Hallendal
2001-11-11 15:26                   ` Tom von Schwerdtner
2001-11-10 14:17           ` Aron Griffis
2001-11-10 14:24             ` Martin Schlemmer

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=1005398351.3250.6.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@cvs.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