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] ebuild for doxygen
Date: Thu Jul 12 14:32:02 2001	[thread overview]
Message-ID: <20010712143131.A16200@cvs.gentoo.org> (raw)
In-Reply-To: <1DCB85BD45DED211B12D009027279E4F476756@murcury>; from SMitchell@phoenix-interactive.com on Thu, Jul 12, 2001 at 03:39:54PM -0400

On Thu, Jul 12, 2001 at 03:39:54PM -0400, Sean Mitchell wrote:
>  <<doxygen-1.2.8.1.ebuild>> 
> 
> This is my first attempt at an ebuild. It builds and installs fine, but when
> I unmerge it there are leftovers (specifically /usr/bin/doxy*). Should I be
> using doexe or exeinto? If so what's the syntax?

The problem is that you are simply doing a "make install", which is incorrect.
You'll notice that all of our ebuilds on CVS that use "make install" use a
special technique to make sure that the files end up at the ${D} root, which is
a temporary directory that contains an image of all the files to be installed
at /.  Your ebuild needs to do this too; you should study the install: portion
of the doxygen Makefile to see if overriding "prefix" or "DESTDIR" will do the
trick.  Then, Portage will be making the modifications to the root filesystem,
rather than your "make install", and will thus record md5sums on everything
that it installs.

Best Regards,

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



  reply	other threads:[~2001-07-12 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 13:44 [gentoo-dev] ebuild for doxygen Sean Mitchell
2001-07-12 14:32 ` Daniel Robbins [this message]
2001-07-12 14:37 ` Ben Lutgens
  -- strict thread matches above, loose matches on Subject: below --
2001-07-13  7:01 Sean Mitchell
2001-07-13  7:27 ` Ben Lutgens
2001-07-13  7:48 Sean Mitchell
2001-07-13  8:00 ` Ben Lutgens

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=20010712143131.A16200@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