From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ReZ6o-0000g6-9H for garchives@archives.gentoo.org; Sat, 24 Dec 2011 21:26:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 32CD521C0B9; Sat, 24 Dec 2011 21:26:11 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id ECE1B21C04D for ; Sat, 24 Dec 2011 21:25:07 +0000 (UTC) Received: by ghrr19 with SMTP id r19so3404558ghr.40 for ; Sat, 24 Dec 2011 13:25:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AptptVpEukq4oymn8D+dTFbLVAg7VeIeNIOVzh5CYBs=; b=o7iBi/w3gbq2UaPJxXPmbI7PjYydxmB77lQrKTCqxvjt1ti/gj3OcEA3sN2cSo9dw6 BgjIY9iFBRpGoTxhU0cuV8K0CA1N6tu0A3v+oVljTnYRikKw6GJEtPnqzRhfUKMtN96b Yo3gUix8Z8STs1pvaO9KF7cLjcxMVDsZq60Gs= Received: by 10.236.178.33 with SMTP id e21mr28076388yhm.4.1324761907419; Sat, 24 Dec 2011 13:25:07 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-122-130.jan.bellsouth.net. [65.0.122.130]) by mx.google.com with ESMTPS id r68sm27016543yhm.18.2011.12.24.13.25.04 (version=SSLv3 cipher=OTHER); Sat, 24 Dec 2011 13:25:06 -0800 (PST) Message-ID: <4EF6432D.40701@gmail.com> Date: Sat, 24 Dec 2011 15:25:01 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111022 Firefox/7.0.1 SeaMonkey/2.4.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Modifying ebuilds, and dependency thoughts between hugin and luminance-hdr. References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 1f5900a9-0ba2-45ee-a124-5208de1206c5 X-Archives-Hash: 07496fded686f13c80140a3aa9a293ae Mark Knecht wrote: > On Sat, Dec 24, 2011 at 12:23 PM, Michael Mol wrote: >> So, media-gfx/luminance-hdr uses hugin's align_image_stack by default. >> Except the ebuild doesn't list a dependency on hugin. I tried >> modifying its ebuild file to add the dependency, but Portage >> complained about a failed digest verification. So I don't know how to >> work around that. >> >> Then there are some additional realizations I had. >> >> 1) Pulling in hugin pulls in gtk and a bunch of additional >> dependencies. Luminance-hdr is a qt app; having a qt app trigger >> pulling in gtk seems silly. >> 2) The tool that luminance-hdr needs is a CLI tool. It doesn't need >> the GUI side of hugin. So it should be possible to build that hugin >> tool without the rest of its GUI. Sounds like another USE flag, or >> perhaps splitting align_image_stack into a separate ebuild and having >> both luminance-hdr and hugin pull that in. >> 3) Luminance-hdr doesn't *need* hugin; it has a builtin tool that >> fills the same role, but behaves a bit differently. It should be >> perfectly possible to remove hugin's tool from the list of options, >> based on a USE flag. >> >> Now, both hugin and luminance-hdr are both tools I've messed with a >> great deal...enough to be frustrated with aspects which lead me to >> dive into their source code to try to fix things. I'm pretty confident >> I could do just about all of it, code-wise and logic-wise. What I >> don't know is anything about ebuild and app development on Gentoo.* >> >> So...where do I go from here? >> >> * This also comes in on my desire to play The Old Republic, but WINE >> 1.3.x has trouble with it. Day job as a Win32 coder comes in handy >> here... >> >> -- >> :wq >> > I haven't tried this in years but from this link: > > http://www.gentoo.org/doc/en/handbook/2004.2/handbook-x86.xml?part=3&chap=6 > > there is this text: > > [QUOTE] > If you are certain that the sources you've fetched and the ebuild > itself are valid, you can regenerate the Manifest and digest- > file using ebuild's digest functionality: > > Code Listing 2.3: Regenerate Manifest and digest > > # ebuild path/to/ebuild digest > [QUOTE] > > HTH, > Mark > > And if I recall correctly, you have to do this again if you sync. You may want to put that in a local overlay or something so that syncs don't change what you are fixing. This is nothing I have done before but have read where others do it this way or at least the way I understood it anyway. Hope that points you in some good direction. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"