[gentoo-ppc-dev] How to bring more ebuilds to ppc

[gentoo-ppc-dev] How to bring more ebuilds to ppc

[David Holm]

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

Hello,
I had an idea. Since there are a number of ebuilds in portage that are only marked x86 or ~x86
but would work just as well (better =) on ppc someone should write a script to find these
ebuilds and compile a list.
We could then post it on the webpage and urge users to help us test packages.

If I was a better scripter I would have written something myself but I believe someone else
would be able to do a much better job of it in less time than I would.

//David Holm

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

Re: [gentoo-ppc-dev] How to bring more ebuilds to ppc

[Thanh Ly]

I started making a C++ app using Qt but it's a command line app and
outputs into a text file. Well it's a little more daunting then I
expected :P but so far I have it iterating through the directories of
/usr/portage and listing sub-directories in each category. Unless
someone finishes this solution before me I'm going to contiune and code
the portion that filters out all the *.ebuild files and searches within
them for 'ppc' and '~ppc' keywords then compile a full list of which
ebuilds have which keyword, all outputted into a text file.
Now to get some sleep and be ready for work tommarow.

Thanh Ly

P.S.
I'm a C++ junkie, if this can be done easier in a scripting language,
great, maybe someone else will come up with the script.

On Tue, 2003-09-02 at 23:28, David Holm wrote:
> Hello,
> I had an idea. Since there are a number of ebuilds in portage that are only marked x86 or ~x86
> but would work just as well (better =) on ppc someone should write a script to find these
> ebuilds and compile a list.
> We could then post it on the webpage and urge users to help us test packages.
> 
> If I was a better scripter I would have written something myself but I believe someone else
> would be able to do a much better job of it in less time than I would.
> 
> //David Holm


--
gentoo-ppc-dev@gentoo.org mailing list

[gentoo-ppc-dev] Re: How to bring more ebuilds to ppc

[Calum Selkirk]

sorry .. ment that to be a list_reply

* Thanh Ly [lycander@ly-tech.com] [2003-09-03 01:53 -0400]:

> I'm a C++ junkie, if this can be done easier in a scripting language,
> great, maybe someone else will come up with the script.

Off the top of my head .. tested in zsh

# find KEYWORDS="ppc"
for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
    do egrep -l "^KEYWORDS=\".+[^~-]ppc.*\"" $i ;
done

# find KEYWORDS="~ppc"
for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
    do egrep -l "^KEYWORDS=\".+~ppc.*\"" $i ;
done

best

cal

--
gentoo-ppc-dev@gentoo.org mailing list

[gentoo-ppc-dev] Re: How to bring more ebuilds to ppc

[Thanh Ly]

On Wed, 2003-09-03 at 03:14, Calum Selkirk wrote:
> Off the top of my head .. tested in zsh
> 
> # find KEYWORDS="ppc"
> for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
>     do egrep -l "^KEYWORDS=\".+[^~-]ppc.*\"" $i ;
> done
> 
> # find KEYWORDS="~ppc"
> for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
>     do egrep -l "^KEYWORDS=\".+~ppc.*\"" $i ;
> done
> 
> best
> 
> cal

Thanks cal, the script works great. I modified it slightly so that it
would output into a text file:

cat find ... <rest of script>
done > ~/output.txt

I put the output files of ppc and ~ppc keyword searches on my webserver
for anyone interested in seeing the list.

This is the list of ebuilds with 'ppc' keyword
http://www.ly-tech.com/unmasked_ppc_ebuilds.txt

This is the list of ebuilds with '~ppc' keyword
http://www.ly-tech.com/masked_ppc_ebuilds.txt

This data is based on my last emerge sync which was Sunday August 31st.
I can update the list once a week if need be.

Regards

Thanh


--
gentoo-ppc-dev@gentoo.org mailing list

[gentoo-ppc-dev] Re: How to bring more ebuilds to ppc

[Calum Selkirk]

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

* Thanh Ly [lycander@ly-tech.com] [2003-09-04 01:24 -0400]:

> Thanks cal, the script works great. I modified it slightly so that it
> would output into a text file:
> 
> cat find ... <rest of script>
> done > ~/output.txt

humm .. no need for cat .. by default output will go to STDOUT but you
rediect to a file like so:

for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
    do egrep -l "^KEYWORDS=\".*~ppc.*\"" $i >| output.txt ;
done

anyhow .. the previously send code was quite wrong (the regular
expression specificly). I was checking for 'one' when in fact in needs
'zero or more' (on the egrep expression). I didn't notice when first
testing as i was consistantly checking for ppc or ~ppc (which rarely
come after the " .. x86 generally occupies that space in the line. 

I've made a proper script (see attatched version 0.1). It should now
work for any arch or ~arch. I've tested it somewhat and it seems ok
(though there could still be bugs). 

So .. for a dated log of ebuilds KEYWORDED ~ppc:

keyworded.sh ~ppc /usr/portage >| output-`date +%F`.txt

best

cal

[-- Attachment #2: keyworded.sh --]
[-- Type: application/x-sh, Size: 929 bytes --]

[-- Attachment #3: Type: text/plain, Size: 41 bytes --]

--
gentoo-ppc-dev@gentoo.org mailing list

Re: [gentoo-ppc-dev] Re: How to bring more ebuilds to ppc

[Nicolas Kaiser]

* "Calum Selkirk" <cselkirk@xs4all.nl>:
> * Thanh Ly [lycander@ly-tech.com] [2003-09-04 01:24 -0400]:
> > cat find ... <rest of script>
> > done > ~/output.txt
> 
> humm .. no need for cat .. by default output will go to STDOUT but you
> rediect to a file like so:
> 
> for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
>     do egrep -l "^KEYWORDS=\".*~ppc.*\"" $i >| output.txt ;
> done

Ah, but you could also increase speed vastly by not using a loop:
(with both of them reading from memory)

$ time for i in `find /usr/portage/ -name "*.ebuild" -print`; do egrep -l "^KEYWORDS=\".*~ppc.*\"" $i; done

real    1m8.892s
user    0m31.380s
sys     0m41.600s

$ time find /usr/portage/ -name "*.ebuild" |xargs egrep -l "^KEYWORDS=\".*~ppc.*\""

real    0m1.053s
user    0m0.810s
sys     0m0.900s


;) Cheers,
n.

-- 
Buffy: Vampires are creeps.
Giles: Yes. That's why one slays them.

--
gentoo-ppc-dev@gentoo.org mailing list

[gentoo-ppc-dev] Re: How to bring more ebuilds to ppc

[Calum Selkirk]

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

* Nicolas Kaiser [nikai@nikai.net] [2003-09-06 09:42 +0200]:

> > for i in `find /usr/portage/${my_target_subdir} -name "*.ebuild" -print` ;
> >     do egrep -l "^KEYWORDS=\".*~ppc.*\"" $i >| output.txt ;
> > done
> 
> Ah, but you could also increase speed vastly by not using a loop:
> (with both of them reading from memory)
>
> $ time for [loop] 
> real    1m8.892s
> user    0m31.380s
> sys     0m41.600s
> 
> $ time find [xargs]
> 
> real    0m1.053s
> user    0m0.810s
> sys     0m0.900s
 
Your probably right but I wouldn't say `time` is a good benchmark, you
will have the results of the egrep cashed from the first run .. you
cheat ;)

Anyhow .. I took sometime today to update the script. You can now search
for -arch and I attempted to impliment no-arch (that is the abscence of
the search_string from the ebuilds) .. It doesn't work :P and I'm not
quite sure, nor do I have time right now to figure out, why exactly.
Prehaps someone else has a clue? It's not alltogher neccessary but would
round the script off and so any pointers welcome (also the sed could
probably be less verbose).

best

cal

[-- Attachment #2: keyworded.sh --]
[-- Type: application/x-sh, Size: 2102 bytes --]

[-- Attachment #3: Type: text/plain, Size: 41 bytes --]

--
gentoo-ppc-dev@gentoo.org mailing list

[gentoo-ppc-dev] XFree-drm-r6 moved to stable

[Kevyn Shortell]

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

After significant testing, and enough failures reported by users of -r3,
and then having them use -r6 successfully, I've moved -r6 to stable.

xfree-drm still has issues with r128, so that hasn't changed, but users
of Radeon 7000, 7500, and 8500s can now use -r6 with the latest kernel.

trance

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-ppc-dev] XFree-drm-r6 moved to stable

[Kevin Geiss]

which latest kernel? :)

the latest benh-sources or the latest stable ppc-sources?

thanks

On Sun September 7 2003 1:26 am, Kevyn Shortell wrote:
> After significant testing, and enough failures reported by users of -r3,
> and then having them use -r6 successfully, I've moved -r6 to stable.
>
> xfree-drm still has issues with r128, so that hasn't changed, but users
> of Radeon 7000, 7500, and 8500s can now use -r6 with the latest kernel.
>
> trance


--
gentoo-ppc-dev@gentoo.org mailing list

Re: [gentoo-ppc-dev] XFree-drm-r6 moved to stable

[Kevyn Shortell]

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

The benh sources. Sorry =)

On Sun, 2003-09-07 at 09:57, Kevin Geiss wrote:
> which latest kernel? :)
> 
> the latest benh-sources or the latest stable ppc-sources?
> 
> thanks
> 
> On Sun September 7 2003 1:26 am, Kevyn Shortell wrote:
> > After significant testing, and enough failures reported by users of -r3,
> > and then having them use -r6 successfully, I've moved -r6 to stable.
> >
> > xfree-drm still has issues with r128, so that hasn't changed, but users
> > of Radeon 7000, 7500, and 8500s can now use -r6 with the latest kernel.
> >
> > trance
> 
> 
> --
> gentoo-ppc-dev@gentoo.org mailing list
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]