tar question re ebuilds

[Tony0945]

I have an overlay ebuild that downloads with git. It downloads on at least one machne (the slowest) but not others.
I'd like very much to create a tarball from the fetch and copy it to distfiles so that I can change the ebuild to use wget from a local server.
Every time I try to tar up the git results, a critical directory is missing.

Ive been using

Code: Select all

tar cfJ palemoon-28.0.2.tar.xz ,  
or
palemoon-28.0.2.tar.xz *

from within the build directory but not all the subdirectories are untarred.
What's the right command?

Alternatively, how to debug git hanging on some machines. Yes, they are both the same version of git.

This may seem trivial but I've been screwing with this for six hours.

Code: Select all

>>> Emerging (1 of 1) www-client/palemoon-28.9.0.2-r4::mybuilds
>>> Unpacking source...
 * Repository id: MoonchildProductions_Pale-Moon.git
 * To override fetched repository properties, use:
 *   EGIT_OVERRIDE_REPO_MOONCHILDPRODUCTIONS_PALE_MOON
 *   EGIT_OVERRIDE_BRANCH_MOONCHILDPRODUCTIONS_PALE_MOON
 *   EGIT_OVERRIDE_COMMIT_MOONCHILDPRODUCTIONS_PALE_MOON
 *   EGIT_OVERRIDE_COMMIT_DATE_MOONCHILDPRODUCTIONS_PALE_MOON
 *
 * Fetching https://github.com/MoonchildProductions/Pale-Moon.git ...

That's as far as it gets. Actually fetches and progresses to "prepare" on my server.

Ate summer, read my voluminous e-mail. Over 45 minutes and still "Fetching https://github.com/MoonchildProductions/Pale-Moon.git"

[charles17]

Can you ebuild <path>/palemoon-28.9.0.2-r4 clean unpack?

[szatox]

Tony, on my first install I couldn't pull that repo, so I just cloned it manually and then restarted emerge.

Code: Select all

du -hsx /usr/portage/distfiles/git3-src/MoonchildProductions_UXP.git
964M	/usr/portage/distfiles/git3-src/MoonchildProductions_UXP.git

You can try copying this repo between your machines to save some bandwidth. Chances are it's under /var/cache/distfiles rather than /usr/portage/distfiles if it's a new installation (or you updated your paths)

[Tony0945]

Can you ebuild <path>/palemoon-28.9.0.2-r4 clean unpack?

Yes

Chances are it's under /var/cache/distfiles rather than /usr/portage/distfiles if it's a new installation (or you updated your paths)

I have them symlinked, but it's no wonder I was able to build on the server. Copying those huge files took some time!

I'm guessing that this repo wa too big for tar. The google told me that SRC_URI can be a space seperated list of files.
So I ran:

Code: Select all

 tar --exclude='platform' -cJf ../palemoon-28.9.0.2.tar.xz  .
 tar -cJf palemoon-platform-28.9.0.2.tar.xz platform

from inside the Source directory. I think I should have done it from the WORK directory because I have to change the ebuild to specify "S=${WORKDIR}, which I don't like to mych, but it's all working!

I copied my new tarballs to my apache directory that I use for my own ebuilds where I am the source coder. I do have a github account but haven't really wrapped my mind around git yet.
SRC_URI points to my server, and then "service apache2 restart" and the other machines just pull from my server instead of the internet.
I use deulore's overlay as a model, but I use different use flags.

If anyone is interested, I pastebinned the ebuild http://dpaste.com/259KX55

Next step is to change the unsupported compilers warning when a supported compiler is in use!

[szatox]

Next step is to change the unsupported compilers warning when a supported compiler is in use!

on stable gentoo it just works. On testing I just copied palemoon's ebuild (and eclass) to local overlay and added 9.3 to supported gcc versions list.
Looks good for now. Maybe next time I'll modify the eclass instead, and symlink ebuils' directory to palemoon, so I don't have to do that for every single bump.

[Tony0945]

I just copied deulore's eclass to my local overlay.

It does work, but always gives the warning even when using a supported compiler.
Here's my fix, pkg_pretend written this afternoon:

Code: Select all

inherit check-reqs xdg-utils fdo-mime toolchain-funcs

EXPORT_FUNCTIONS pkg_pretend pkg_preinst pkg_postinst pkg_postrm pkg_setup


###
# Package
###

palemoon-5-r2_pkg_pretend() {
        local i gv
        # Ensure that we have enough disk space to compile:
        CHECKREQS_DISK_BUILD=${REQUIRED_BUILDSPACE}
        check-reqs_pkg_setup

        # Ensure that we are on a supported compiler profile:
        einfo "Checking compiler profile..."
        if [ "$(tc-get-compiler-type)" != "gcc" ]; then
                unsupported_compiler_error "$(tc-get-compiler-type)"
                die
        fi

        gv=$(gcc-version)
        for i in $GCC_SUPPORTED_VERSIONS
        do
                if [ "$gv" == "$i" ]; then
                        return
                fi
        done
        # it's gcc, but not a supported version
        if [ "$PALEMOON_ENABLE_UNSUPPORTED_COMPILERS" == 1 ] ; then
                unsupported_compiler_warning "$(tc-get-compiler-type)"
        else
                unsupported_compiler_error "$(tc-get-compiler-type)"
                die
        fi
}

palemoon-5-r2_pkg_preinst() {
        xdg_icon_savelist
}

palemoon-5-r2_pkg_postinst() {
        # Update mimedb for the new .desktop file:
        fdo-mime_desktop_database_update
        xdg_icon_cache_update
}

That's revision 2 because revision 1 only switched from the gnome functions to the xdg functions for compliance with EAPI 7.

[Tony0945]

python2 is hard coded in the ebuild. Any idea if python3 works?