Re: [gentoo-dev] new guides

[AGottinger@t-online.de (Achim Gottinger)]

> The freeze module will covert the python code to c and then compile it.

Sounds good in theory, does it work better that perl->c?

> I think we can also look at using stripped down version of Python, like
> stackless or pippy. 

Yes that must be evaluated.

 I guess I'm just very pro-python.  We've developed
> a great system that through the use of a very-high level scripting
> language provides an easy framework for hacking and extensibility.  I'd
> hate to see that lost.

As long as daniel lives, you whoun't see that lost. The plan is to
convert parts of
the ebuild python code to c++ once it is stable. Do you plan to hack
things like the
dependencie system? So finaly the core of ebuild will be c++ code used
by a python module.
Then it is possible to write modules for ebuild in other languages too.
> 
> Since time is limited, why don't we just concentrate on what we've
> always been doing?  I figure that if can publish an API, then others can
> develop ebuild in other languages.
> 
I do not see a sense in using other languages than bash for ebuild's
functions, but
it whould be great to have a perl module from which I can access ebuilds
functions.
Of cause we currently concentrate on what we've always been doing.
I'm reworking all our packages since two month to make intensive use of
the USE variables.
Once I'm finished we should be able to use USE as a global config file
for all packages.
So for example if you set "mysql" in USE all packages that can be linked
against mysql
get linked against it. I think this is usefull for embedded systems too,
because it can
reduce the package's size immense. There is no need for native languages
support, pam or
readline on an internet radio.
Unfortunately all this is much more time-consumning as I thought and
that is a main cause
why there was no new release in the past. But once it is finished I
swear that it will be real
fun.

> : BTW: Jerry, are you still headbanging or did you get gentoo working now?
> 
> No.  Unfortunately, I've become the latest dot-com casualty.  
Urgh, sorry to hear that, hope you get a new job soon.

So, the
> Vaio z505 had to go back.  I went to a computer show over the weekend
> and picked up the parts to put together a 1GHz Athlon system (I even
> picked up a pcmcia bay so I can still try and get laptop portages made).
> So, it's back to the drawing board for figuring out how to bootstrap
> this puppy.

I made a package for yard, which is a nice system for building rescue
and install discs. Simplified
you pass a list of binraies you want to have on a disc and yard finds te
required libs and builds 
a working image for you. Debian uses a nice script to reduce the size of
the shared libraries for such
a disc by building the shared libs from _pic.a archives with only the
required funtions. This can reduce
for exanple glibc's size to nearly the half.
The problem is that yard currently has the path to the config stuff
hardcoded, so it must be hacked to
read an env var or an parameter (should not be difficult).
Once this is done, I think it's even good for making images for embedded
systems.
Additionaly I try to use syslinux for the boot disc. Hopefully this
works better than our current system.
Once more it's more time-consuming than expected but real fun in the
end.

All the trials we made for a week to get gentoo running on your vaio
where tested here on an Athlon system,
so hopefully it will work on your system too.
Maybe I can upload new snapshot releases for build and sys this week.

bye achim~

> 
>         --Jerry
> 
> name:  Jerry Alexandratos         ||  Open-Source software isn't a
> phone: 703.599.6023               ||  matter of life or death...
> email: jerry@thehutt.org          ||  ...It's much more important
>                                   ||  than that!
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev