[gentoo-user] where is the functionality of etcat

[gentoo-user] where is the functionality of etcat

[Rudmer van Dijk]

etcat is deprecated in favor of equery but equery does not have a 
functionality like `etcat -v <package>` (listing all available versions of a 
package). I used it quite often and have been struggling with equery ever 
since etcat is deprecated... Are there plans to build this functionality into 
equery? if not, why??

	Rudmer
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] where is the functionality of etcat

[Holly Bostick]

Rudmer van Dijk schreef:
> etcat is deprecated in favor of equery but equery does not have a 
> functionality like `etcat -v <package>` (listing all available versions of a 
> package). I used it quite often and have been struggling with equery ever 
> since etcat is deprecated... Are there plans to build this functionality into 
> equery? if not, why??
> 
> 	Rudmer

Possibly because you can do the same with eix (emerge eix):

 eix gnome-games
* gnome-extra/gnome-games
     Available versions:  1.4.0.3-r3 2.4.2 2.6.2 2.8.1 2.8.1-r1 2.8.2
2.8.3 2.10.0 ~2.10.1
     Installed:           2.10.1
     Homepage:            http://www.gnome.org/
     Description:         Collection of games for the GNOME desktop

* gnome-extra/gnome-games-extra-data
     Available versions:  2.8.0 2.10.0
     Installed:           2.10.0
     Homepage:            http://www.gnome.org/
     Description:         Optional additional graphics for gnome- games


If that's of any help to you :-) .

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

Re: [gentoo-user] where is the functionality of etcat

[Renat Golubchyk]

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

On Mon, 11 Jul 2005 23:25:06 +0200 Rudmer van Dijk
<rudmer@legolas.dynup.net> wrote:
> etcat is deprecated in favor of equery but equery does not have a 
> functionality like `etcat -v <package>` (listing all available
> versions of a  package). I used it quite often and have been
> struggling with equery ever  since etcat is deprecated... Are there
> plans to build this functionality into  equery? if not, why??

It is already in there, people just tend to overlook it ;-) Run
"equery list -p package", for more information run "equery list --help"
or generally "equery <command> --help". If you run "equery --help" you
will notice that equery has global options and local options which do
some nice stuff.

Cheers,
Renat

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] where is the functionality of etcat

[Andreas Claesson]

On 7/11/05, Rudmer van Dijk <rudmer@legolas.dynup.net> wrote:
> etcat is deprecated in favor of equery but equery does not have a
> functionality like `etcat -v <package>` (listing all available versions of a
> package). I used it quite often and have been struggling with equery ever
> since etcat is deprecated... Are there plans to build this functionality into
> equery? if not, why??
> 

Doesn't 'equery list -p <package>' do what you want?  

$ equery list -p gentoo-sources
[ Searching for package 'gentoo-sources' in all categories among: ]
 * installed packages
[I--] [  ] sys-kernel/gentoo-sources-2.6.11-r11 (2.6.11-r11)
[I--] [  ] sys-kernel/gentoo-sources-2.6.12-r4 (2.6.12-r4)
 * Portage tree (/usr/portage)
[-P-] [M~] sys-kernel/gentoo-sources-2.6.12-r3 (2.6.12-r3)
[-P-] [  ] sys-kernel/gentoo-sources-2.6.9-r9 (2.6.9-r9)
[-P-] [  ] sys-kernel/gentoo-sources-2.4.28-r9 (2.4.28-r9)
[-P-] [  ] sys-kernel/gentoo-sources-2.6.10-r6 (2.6.10-r6)
[-P-] [  ] sys-kernel/gentoo-sources-2.6.11-r8 (2.6.11-r8)

/Andreas

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] where is the functionality of etcat

[Rudmer van Dijk]

On Monday 11 July 2005 23:47, Renat Golubchyk wrote:
> On Mon, 11 Jul 2005 23:25:06 +0200 Rudmer van Dijk
>
> <rudmer@legolas.dynup.net> wrote:
> > etcat is deprecated in favor of equery but equery does not have a
> > functionality like `etcat -v <package>` (listing all available
> > versions of a  package). I used it quite often and have been
> > struggling with equery ever  since etcat is deprecated... Are there
> > plans to build this functionality into  equery? if not, why??
>
> It is already in there, people just tend to overlook it ;-) Run
> "equery list -p package", for more information run "equery list --help"
> or generally "equery <command> --help". If you run "equery --help" you
> will notice that equery has global options and local options which do
> some nice stuff.

thanks! I should have RTFM better than I did...

Holly: eix is probably not it, since it looks like it does not show the 
availability of the package (masked+keyword), but thanks for the suggestion!

	Rudmer
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] where is the functionality of etcat

[Holly Bostick]

Rudmer van Dijk schreef:
> 
> Holly: eix is probably not it, since it looks like it does not show the 
> availability of the package (masked+keyword), but thanks for the suggestion!
> 
> 	Rudmer

Actually, it most certainly does; keyworded packages are shown in brown
with a ~ in front, masked packages are listed in red with a [M] in front.

Of course you can use what suits you best; just wanted to clear up the
misconception.

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

Re: [gentoo-user] where is the functionality of etcat

[Tom Wesley]

[-- Attachment #1.1: Type: text/plain, Size: 1650 bytes --]

On Tue, 12 Jul 2005 19:26:14 +0200
Holly Bostick <motub@planet.nl> wrote:

> Rudmer van Dijk schreef:
> > 
> > Holly: eix is probably not it, since it looks like it does not show the 
> > availability of the package (masked+keyword), but thanks for the suggestion!
> > 
> > 	Rudmer
> 
> Actually, it most certainly does; keyworded packages are shown in brown
> with a ~ in front, masked packages are listed in red with a [M] in front.
> 
> Of course you can use what suits you best; just wanted to clear up the
> misconception.
> 
> Holly

I haven't seen anyone post this script as yet.  It's by ciaranm and is
very useful when people ask on irc why a certain package version can't
be installed on their arch.

Sample output:
tom@tom ~ 0 0.67 $ eshowkw
gnome Keywords for gnome-base/gnome:

            | a a a h i m m p p p p s s s x x x x
            | l m r p a 6 i p p p p 3 h p 8 8 8 8
            | p d m p 6 8 p c c c c 9   a 6 6 6 6
            | h 6   a 4 k s   6 - - 0   r   - - -
            | a 4             4 m o     c   f o o
            |                   a d         b b d
            |                   c           s s
            |                   o           d d
            |                   s
------------+------------------------------------
1.4-r3      |               -           + +
2.8.2       | + +   + +   + +           + +
2.8.3-r1    | ~ +   + +   ~ +           + +
2.10        |   ~     ~     ~ ~         ~ ~
2.10-r1     | + +   + ~     + ~         + +
2.10.1_pre0 |   ~           ~ ~         ~ ~

Hope this is helpful to someone ;)

-- 
Tom Wesley <tom@tomaw.org>

[-- Attachment #1.2: eshowkw --]
[-- Type: application/octet-stream, Size: 9416 bytes --]

#!/bin/bash
# vim: set sw=4 sts=4 et tw=80 :

# Author:        Ciaran McCreesh <ciaranm@gentoo.org>
# Purpose:       Display ebuild keywords in a graphical form
# Invocation:    eshowkw [ packagename ] (defaults to current directory if no
#                packagename is provided)

shopt -s extglob

PID_TO_KILL=$$

die() {
    echo "$@" 1>&2
    kill $PID_TO_KILL
}

trap 'exit 250' 15

get_portage_dir() {
    local dir
    if [[ -z ${portage_dir_cache} ]] ; then
        for dir in "${HOME}/cvs/gentoo-x86" "/usr/portage" ; do
            [[ -d ${dir}/profiles ]] && portage_dir_cache=${dir} && break
        done
    fi
    [[ -z ${portage_dir_cache} ]] && portage_dir_cache=$(portageq portdir )
    export portage_dir_cache
    echo ${portage_dir_cache}
}

version_sort() {
    local items= left=0
    items=( $@ )

    while [[ ${left} -lt ${#items[@]} ]] ; do
        local lowest_idx=${left}
        local idx=$(( ${lowest_idx} + 1 ))
        while [[ ${idx} -lt ${#items[@]} ]] ; do
            version_compare "${items[${lowest_idx}]}" "${items[${idx}]}"
            [[ $? -eq 3 ]] && lowest_idx=${idx}
            idx=$(( ${idx} + 1 ))
        done
        local tmp=${items[${lowest_idx}]}
        items[${lowest_idx}]=${items[${left}]}
        items[${left}]=${tmp}
        left=$(( ${left} + 1 ))
    done
    echo ${items[@]}
}

version_compare() {
    local ver_a=${1} ver_b=${2} parts_a parts_b cur_idx_a=0 cur_idx_b=0
    parts_a=( $(get_all_version_components "${ver_a}" ) )
    parts_b=( $(get_all_version_components "${ver_b}" ) )

    ### compare number parts.
    local inf_loop=0
    while true ; do
        # grab the current number components
        local cur_tok_a=${parts_a[${cur_idx_a}]}
        local cur_tok_b=${parts_b[${cur_idx_b}]}

        # number?
        if [[ -n ${cur_tok_a} ]] && [[ -z ${cur_tok_a//[[:digit:]]} ]] ; then
            cur_idx_a=$(( ${cur_idx_a} + 1 ))
            [[ ${parts_a[${cur_idx_a}]} == "." ]] \
                && cur_idx_a=$(( ${cur_idx_a} + 1 ))
        else
            cur_tok_a=""
        fi

        if [[ -n ${cur_tok_b} ]] && [[ -z ${cur_tok_b//[[:digit:]]} ]] ; then
            cur_idx_b=$(( ${cur_idx_b} + 1 ))
            [[ ${parts_b[${cur_idx_b}]} == "." ]] \
                && cur_idx_b=$(( ${cur_idx_b} + 1 ))
        else
            cur_tok_b=""
        fi

        # done with number components?
        [[ -z ${cur_tok_a} ]] && [[ -z ${cur_tok_b} ]] && break

        # to avoid going into octal mode, strip any leading zeros. otherwise
        # bash will throw a hissy fit on versions like 6.3.068.
        cur_tok_a=${cur_tok_a##+(0)}
        cur_tok_b=${cur_tok_b##+(0)}

        # if a component is blank, make it zero.
        [[ -z ${cur_tok_a} ]] && cur_tok_a=0
        [[ -z ${cur_tok_b} ]] && cur_tok_b=0

        # compare
        [[ ${cur_tok_a} -lt ${cur_tok_b} ]] && return 1
        [[ ${cur_tok_a} -gt ${cur_tok_b} ]] && return 3
    done

    ### number parts equal. compare letter parts.
    local letter_a=
    letter_a=${parts_a[${cur_idx_a}]}
    if [[ ${#letter_a} -eq 1 ]] && [[ -z ${letter_a/[a-z]} ]] ; then
        cur_idx_a=$(( ${cur_idx_a} + 1 ))
    else
        letter_a="@"
    fi

    local letter_b=
    letter_b=${parts_b[${cur_idx_b}]}
    if [[ ${#letter_b} -eq 1 ]] && [[ -z ${letter_b/[a-z]} ]] ; then
        cur_idx_b=$(( ${cur_idx_b} + 1 ))
    else
        letter_b="@"
    fi

    # compare
    [[ ${letter_a} < ${letter_b} ]] && return 1
    [[ ${letter_a} > ${letter_b} ]] && return 3

    ### letter parts equal. compare suffixes in order.
    local suffix rule part r_lt r_gt
    for rule in "alpha=1" "beta=1" "pre=1" "rc=1" "p=3" "r=3" ; do
        suffix=${rule%%=*}
        r_lt=${rule##*=}
        [[ ${r_lt} -eq 1 ]] && r_gt=3 || r_gt=1

        local suffix_a=
        for part in ${parts_a[@]} ; do
            [[ ${part#${suffix}} != ${part} ]] && \
                [[ -z ${part##${suffix}*([[:digit:]])} ]] && \
                suffix_a=${part#${suffix}}0
        done

        local suffix_b=
        for part in ${parts_b[@]} ; do
            [[ ${part#${suffix}} != ${part} ]] && \
                [[ -z ${part##${suffix}*([[:digit:]])} ]] && \
                suffix_b=${part#${suffix}}0
        done

        [[ -z ${suffix_a} ]] && [[ -z ${suffix_b} ]] && continue

        [[ -z ${suffix_a} ]] && return ${r_gt}
        [[ -z ${suffix_b} ]] && return ${r_lt}

        # avoid octal problems
        suffix_a=${suffix_a##+(0)} ; suffix_a=${suffix_a:-0}
        suffix_b=${suffix_b##+(0)} ; suffix_b=${suffix_b:-0}

        [[ ${suffix_a} -lt ${suffix_b} ]] && return 1
        [[ ${suffix_a} -gt ${suffix_b} ]] && return 3
    done

    ### no differences.
    return 2
}

get_all_version_components() {
    local ver_str=${1} result result_idx=0
    result=( )

    while [[ -n "$ver_str" ]] ; do
        case "${ver_str:0:1}" in
            # number: parse whilst we have a number
            [[:digit:]])
                result[$result_idx]="${ver_str%%[^[:digit:]]*}"
                ver_str="${ver_str##+([[:digit:]])}"
                result_idx=$(($result_idx + 1))
                ;;

            # separator: single character
            [-_.])
                result[$result_idx]="${ver_str:0:1}"
                ver_str="${ver_str:1}"
                result_idx=$(($result_idx + 1))
                ;;

            # letter: grab the letters plus any following numbers
            [[:alpha:]])
                local not_match="${ver_str##+([[:alpha:]])*([[:digit:]])}"
                result[$result_idx]=${ver_str:0:$((${#ver_str} - ${#not_match}))}
                ver_str="${not_match}"
                result_idx=$(($result_idx + 1))
                ;;

            # huh?
            *)
                result[$result_idx]="${ver_str:0:1}"
                ver_str="${ver_str:1}"
                result_idx=$(($result_idx + 1))
                ;;
        esac
    done

    echo ${result[@]}
}

get_package_dir() {
    if [[ -z ${1} ]] ; then
        pwd
        return 0
    fi

    if [[ -d ${1} ]] ; then
        readlink -f ${1}
        return 0
    fi

    get_portage_dir 1>/dev/null
    if [[ ${1/\/} != ${1} ]] ; then
        local d=$(get_portage_dir )/${1}
        if [[ -d ${d} ]] ; then
            echo ${d}
            return 0
        fi
    else
        local d
        d=( $(echo $(get_portage_dir )/*-*/${1} ) )
        if [[ ${#d[@]} -gt 1 ]] ; then
            die "${1} is ambiguous"
        elif [[ -d ${d[0]} ]] ; then
            echo ${d[0]}
            return 0
        fi
    fi

    return 1
}

repeat() {
    local i
    for (( i=0 ; i < ${1} ; i=$(( ${i} + 1 )) )) ; do
        echo -n "${2}"
    done
}

get_keywords() {
    (
        inherit() { :; }
        source ${1} 2>/dev/null
        echo ${KEYWORDS}
    )
}

colourise() {
    case "${1}" in
        \*)
            echo -n -e "\033[0;31m*\033[0;0m"
            ;;
        +)
            echo -n -e "\033[0;32m+\033[0;0m"
            ;;
        -)
            echo -n -e "\033[0;31m-\033[0;0m"
            ;;
        \~)
            echo -n -e "\033[0;33m~\033[0;0m"
            ;;
        *)
            echo -n "${1}"
            ;;
    esac
}

show_keyword_diagram() {
    echo -n -e "Keywords for \033[1;34m"
    local title=$(readlink -f $(pwd ) )
    title=${title#$(readlink -f ../.. )/*( )}
    echo -n "${title}"
    echo -e "\033[0;0m:"
    echo

    local archs= arch_length=0 arch=
    archs=( $(< $(get_portage_dir )/profiles/arch.list ) )
    for arch in "${archs[@]}" ; do
        [[ ${#arch} -gt ${arch_length} ]] && arch_length=${#arch}
    done

    local versions= pkgname= version_length=0 version=
    pkgname=$(basename $(readlink -f ./ ) )
    versions=( $(for e in $(echo *.ebuild ) ; do \
            [[ -f ${e} ]] && echo ${e} | sed -e 's/\.ebuild$//g' \
                    -e "s/^${pkgname}-//g" ; \
            done ) )
    versions=( $(version_sort ${versions[@]} ) )
    for version in "${versions[@]}" ; do
        [[ ${#version} -gt ${version_length} ]] && version_length=${#version}
    done

    local i
    for (( i = 0 ; i < ${arch_length} ; i=$(( ${i} + 1 )) )) ; do
        repeat ${version_length} " "
        echo -n " | "
        for arch in "${archs[@]}" ; do
            arch="${arch:${i}:1}"
            echo -n "${arch:- } "
        done
        echo
    done

    repeat ${version_length} "-"
    echo -n "-+"
    repeat ${#archs[@]} "--"
    echo

    for version in "${versions[@]}" ; do
        echo -n "${version}"
        repeat $(( ${version_length} - ${#version} )) " "
        echo -n " | "

        local keyword keywords
        keywords=( $(get_keywords "${pkgname}-${version}.ebuild" ) )
        for arch in "${archs[@]}" ; do
            local display=" "
            [[ ${keywords[@]/-\*} != ${keywords[@]} ]] && display="*"
            for keyword in "${keywords[@]}" ; do
                [[ ${arch} == "${keyword#[~-]}" ]] && \
                    display=${keyword:0:1} && \
                    break;
            done
            [[ -z ${display#[~ *-]} ]] || display="+"
            echo -n "$(colourise "${display}" ) "
        done

        echo
    done
}

main() {
    local dir=$(get_package_dir "${1}" )
    [[ -z ${dir} ]] && die "Couldn't find '${1}'"
    cd ${dir}
    [[ $(echo *.ebuild ) != "*.ebuild" ]] || die "No ebuilds in ${dir}"
    show_keyword_diagram
    true
}

main "$@"


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: where is the functionality of etcat

[James]

Holly Bostick <motub <at> planet.nl> writes:


> > Holly: eix is probably not it, since it looks like it does not show the 
> > availability of the package (masked+keyword), but thanks for the suggestion!

> Actually, it most certainly does; keyworded packages are shown in brown
> with a ~ in front, masked packages are listed in red with a [M] in front.

> Of course you can use what suits you best; just wanted to clear up the
> misconception.


Well 'eix zoneminder' shows '~0.9.12  ~1.21.2'
both in brown.

emerge -s zoneminders shows
that it is masked in red and only 1.21.2. is available.

Maybe my color scheme is messed up?

James




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: where is the functionality of etcat

[Holly Bostick]

James schreef:
> Holly Bostick <motub <at> planet.nl> writes:
> 
> 
> 
>>>Holly: eix is probably not it, since it looks like it does not show the 
>>>availability of the package (masked+keyword), but thanks for the suggestion!
> 
> 
>>Actually, it most certainly does; keyworded packages are shown in brown
>>with a ~ in front, masked packages are listed in red with a [M] in front.
> 
> 
>>Of course you can use what suits you best; just wanted to clear up the
>>misconception.
> 
> 
> 
> Well 'eix zoneminder' shows '~0.9.12  ~1.21.2'
> both in brown.
> 
> emerge -s zoneminders shows
> that it is masked in red and only 1.21.2. is available.
> 
> Maybe my color scheme is messed up?
> 
> James
> 
> 
> 
> 

According to packages.gentoo.org, both zoneminder 0.9.12 and 1.21.2 are
keyword masked, so the output is correct (for x86).

Esearch shows only the last version, and doesn't distinguish between
hard and keyword masking; perhaps emerge -s is the same.

Also, it helps to remember to do an update-eix after an esync, so that
new or updated packages are added to the eix database.

Other than that, I don't see a problem.

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

Re: [gentoo-user] where is the functionality of etcat

[Rudmer van Dijk]

On Tuesday 12 July 2005 19:50, Tom Wesley wrote:
> On Tue, 12 Jul 2005 19:26:14 +0200
>
> I haven't seen anyone post this script as yet.  It's by ciaranm and is
> very useful when people ask on irc why a certain package version can't
> be installed on their arch.
>
> Sample output:
> tom@tom ~ 0 0.67 $ eshowkw
>
> gnome Keywords for gnome-base/gnome:
>             | a a a h i m m p p p p s s s x x x x
>             | l m r p a 6 i p p p p 3 h p 8 8 8 8
>             | p d m p 6 8 p c c c c 9   a 6 6 6 6
>             | h 6   a 4 k s   6 - - 0   r   - - -
>             | a 4             4 m o     c   f o o
>             |                   a d         b b d
>             |                   c           s s
>             |                   o           d d
>             |                   s
>
> ------------+------------------------------------
> 1.4-r3      |               -           + +
> 2.8.2       | + +   + +   + +           + +
> 2.8.3-r1    | ~ +   + +   ~ +           + +
> 2.10        |   ~     ~     ~ ~         ~ ~
> 2.10-r1     | + +   + ~     + ~         + +
> 2.10.1_pre0 |   ~           ~ ~         ~ ~
>
> Hope this is helpful to someone ;)

nice!
don't think it is really useful for me, I have two archs (amd64 and x86) but 
have good access to both machines. if you maintain more archs than this can 
be very usefull. Is this in some (dev-)package? maybe something for 
gentoolkit??

	Rudmer
-- 
gentoo-user@gentoo.org mailing list