public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Paludis and Emacs overlay
Date: Wed, 18 Jul 2007 09:46:22 +0100	[thread overview]
Message-ID: <20070718094622.6256c7b4@snowflake> (raw)
In-Reply-To: <20070717213150.65d846a8@luna.home>

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

On Tue, 17 Jul 2007 21:31:50 +0200
Christian Faulhammer <opfer@gentoo.org> wrote:
> I just read Donnie's nice article [1] and went through the comments.
> One saying
> 
> "After switching to paludis, I installed layman, and used it to
> kick-start some of the overlays.gentoo.org stuff. Paludis expects more
> discipline, apparently, and there was some manual effort to configure,
> say, the emacs overlay. Had to create several files and directories to
> silence the error traces."
> 
> Can anyone tell me what those messages actually are to fix it?

Hrm, I don't see any warnings for the emacs overlay using the following
(native, not Portage) configuration:

location = /var/paludis/repositories/emacs
format = ebuild
sync = svn+http://overlays.gentoo.org/svn/proj/emacs/emacs-overlay
master_repository = gentoo
write_cache = /var/cache/paludis/metadata/

Usually when people get errors with an overlay it's because of a
missing profiles/repo_name file, which isn't the case here.

-- 
Ciaran McCreesh


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2007-07-18  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070717213150.65d846a8@luna.home>
2007-07-18  8:46 ` Ciaran McCreesh [this message]
2007-07-18 10:38   ` [gentoo-dev] Paludis and Emacs overlay Ulrich Mueller

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=20070718094622.6256c7b4@snowflake \
    --to=ciaranm@ciaranm.org \
    --cc=gentoo-dev@lists.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