public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] rc-update and /etc/rc.d/config/functions
Date: Mon Sep  3 22:53:02 2001	[thread overview]
Message-ID: <20010903225238.I20781@cvs.gentoo.org> (raw)
In-Reply-To: <20010903222707.C3501@emt-p.org>; from insyte@emt-p.org on Mon, Sep 03, 2001 at 10:27:08PM -0500

On Mon, Sep 03, 2001 at 10:27:08PM -0500, Ben Beuchler wrote:

> ================
> mazer openssh # emerge openssh-2.9_p2-r2.ebuild 
> Calculating dependencies.
> 
> !!! Portage had a problem processing this file:
> !!! /usr/portage/net-misc/openssh/openssh-2.9_p2-r2.ebuild
> 
> /usr/sbin/ebuild.sh: /usr/portage/net-misc/openssh/openssh-2.9_p2-r2.ebuild:
> line 57: syntax error near unexpected token `}'
> /usr/sbin/ebuild.sh: /usr/portage/net-misc/openssh/openssh-2.9_p2-r2.ebuild:
> line 57: `}'

OK, openssh-2.9_p2-r2 had yet another bug (empty function, thanks to commenting)
out a line, and bash doesn't like empty functions.  Now fixed on rsync and cvs.

> What is the current status with init scripts?  I understand they're in
> considerable flux these days.  For example, which location is correct for the
> 'functions' file?  /etc/rc.d/config/functions or /etc/init.d/functions.sh?

For 1.0_rc6+, /etc/init.d/functions.sh

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			



      reply	other threads:[~2001-09-04  4:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 19:00 [gentoo-dev] rc-update and /etc/rc.d/config/functions Ben Beuchler
2001-09-03 20:49 ` Daniel Robbins
2001-09-03 20:52   ` Ben Beuchler
2001-09-03 20:57     ` Daniel Robbins
2001-09-03 21:28       ` Ben Beuchler
2001-09-03 22:53         ` Daniel Robbins [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=20010903225238.I20781@cvs.gentoo.org \
    --to=drobbins@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