public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Locale definition for OpenOffice
Date: Sun, 14 Aug 2005 13:52:46 +0200	[thread overview]
Message-ID: <42FF308E.1060305@planet.nl> (raw)
In-Reply-To: <200508141216.52170.uwix@iway.na>

Uwe Thiem schreef:
> Hi folks,
> 
> I am in the process of writing the locale definition for Namibia for 
> OpenOffice. Before I submit it, I'd like to test it locally. I thought of 
> doing it this way:
> 
> Untar OOo_1.1.4_source.tar.gz manually.
> Add my locale definition to resulting source tree.
> Hack the Makefile in that directory (seems easy enough).
> Tar everything up again and mv it to /usr/portage/distfiles.
> Emerge OO again.
> 
> Certainly I have to adjust some checksums before emerging it again. When I do 
> a "md5sum /usr/portage/distfiles/OOo_1.1.4_source.tar.gz" (before changing 
> anything, of course), the resulting checksum does not match any of those in 
> the Manifest. I am unsure now what I have to adjust. The only file I am going 
> to change is the tarball itself. Anybody to the rescue? ;-)
> 
> Uwe
>  

First of all, I would suggest copying the original ebuild to
/usr/local/portage/app-office/openoffice (or wherever you keep your
overlay), along with any files in the /files folder (and the folder
itself) in Portage (so if the build is normally patched by Gentoo, those
patches are available to the overlay build as well).

I would then revise the ebuild to change the name to something that
specifies that this is your ebuild and not the one in portage
(openoffice-1.1.4-ut, or whatever. IIrc, you also have to edit the
header of the ebuild to conform with the new name, and possibly also the
'name' of the tarball within the ebuild, if you change the tarball name).

Tar up your revised source (you might have to/want to name it
OOo_1.1.4_source-ut.tar.gz, which wouldn't be a bad idea in any case) in
/usr/portage/distfiles.

Then digest the overlay ebuild with

ebuild
/usr/local/portage/app-office/openoffice/openoffice-1.1.4-ut.ebuild digest

This will create a manifest using the newly-generated checksum for your
ebuild and tarball.

Emerge OOo normally-- since your ebuild is newer than the one in
Portage, it should be the one emerged.

These instructions should be generally valid, but possibly inexact,
since I don't do this that often, but I've done it often enough to
generally remember how it's done when necessary.

Of course all this pre-supposes that you have an overlay set up in your
/etc/make.conf, but I would imagine that you do, if you're making these
sort of adjustments for upstream programs.

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-14 12:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 11:16 [gentoo-user] Locale definition for OpenOffice Uwe Thiem
2005-08-14 11:52 ` Holly Bostick [this message]
2005-08-14 17:17   ` Uwe Thiem
2005-08-14 11:53 ` Edward Catmur

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=42FF308E.1060305@planet.nl \
    --to=motub@planet.nl \
    --cc=gentoo-user@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