[gentoo-user] Locale definition for OpenOffice

[gentoo-user] Locale definition for OpenOffice

[Uwe Thiem]

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
 
-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Locale definition for OpenOffice

[Holly Bostick]

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

Re: [gentoo-user] Locale definition for OpenOffice

[Edward Catmur]

On Sun, 2005-08-14 at 12:16 +0100, Uwe Thiem wrote:
> 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

Checksums for distfiles are in files/digest-${P}, not in Manifest.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Locale definition for OpenOffice

[Uwe Thiem]

On 14 August 2005 12:52, Holly Bostick wrote:
> 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.

I usually don't but have no choice with OO, need a couple of settings. 
Nonetheless, I do have an overlay from the days when deltup was not in 
portage. So I am lucky here.

Anyway, thanks a lot, Holly! 

Uwe

-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list