[gentoo-dev] allowing configuration of builds?

[gentoo-dev] allowing configuration of builds?

[Pete Gavin]

Hi,

I was thinking about a way we could allow configuration information to
be passed to the ebuild scripts at build time. This information could be
stored in the package database, so that doing "ebuild
/var/db/pkg/{whatever}/{whatever}.ebuild remerge" would create the exact
same package as before. We could make it so that if you do something
like "ebuild {path-to-ebuild-file} query" it will tell you what
configuration options are available, then you could set those options on
the ebuild command line. That way, say, for example, there are packages
that can use gnome, but don't require it, you could do

ebuild {ebuild-file} merge without-gnome

or some such to build it w/o gnome support. The ebuild file will check
for these options and set the appropriate command line switches to
configure. You could even cause these options to apply different
patches. Has anyone else thought about this?

Pete

Re: [gentoo-dev] allowing configuration of builds?

[Pete Gavin]

On Mon, Feb 05, 2001 at 02:42:08PM -0700, Pete Gavin wrote:
> Hi,
> 
> I was thinking about a way we could allow configuration information to
> be passed to the ebuild scripts at build time. This information could be
> stored in the package database, so that doing "ebuild
> /var/db/pkg/{whatever}/{whatever}.ebuild remerge" would create the exact
> same package as before. We could make it so that if you do something
> like "ebuild {path-to-ebuild-file} query" it will tell you what
> configuration options are available, then you could set those options on
> the ebuild command line. That way, say, for example, there are packages
> that can use gnome, but don't require it, you could do
> 
> ebuild {ebuild-file} merge without-gnome
> 
> or some such to build it w/o gnome support. The ebuild file will check
> for these options and set the appropriate command line switches to
> configure. You could even cause these options to apply different
> patches. Has anyone else thought about this?
>

Oh, yeah, for example, right now we've got 3 different packages for
emacs; emacs-nogui, emacs-x11, & emacs-motif. With options like this, we
could make it into one package.

Pete
 

Re: [gentoo-dev] allowing configuration of builds?

[Achim Gottinger]

Pete Gavin wrote:

> Hi,
>
> I was thinking about a way we could allow configuration information to
> be passed to the ebuild scripts at build time. This information could be
> stored in the package database, so that doing "ebuild
> /var/db/pkg/{whatever}/{whatever}.ebuild remerge" would create the exact
> same package as before. We could make it so that if you do something
> like "ebuild {path-to-ebuild-file} query" it will tell you what
> configuration options are available, then you could set those options on
> the ebuild command line. That way, say, for example, there are packages
> that can use gnome, but don't require it, you could do
>
> ebuild {ebuild-file} merge without-gnome
>
> or some such to build it w/o gnome support. The ebuild file will check
> for these options and set the appropriate command line switches to
> configure. You could even cause these options to apply different
> patches. Has anyone else thought about this?

Yes I did but that whould make resolving dependencies more difficult.
There might be situations like

package a requires package b (with gnome support).

Such cases are not covered by our current dependencie approach.

So dependencies must look like

a.ebuild
---------
DEPEND="gnome? ( b(gnome) )
                   !gnome? ( b )"

Which means if a should build with gnome support then we need b with gnome
support.
If a should be build without gnome support we need b (with our without
gnome support).

At the moment we focus on stability and do not want to add more features to
ebuild.
Once packages are all correct, secure and dependencies are all working we
want to
improve configuration.

Daniel is working on a next gen ebuild. I don't think such major
modifications will be made
to our current ebuild but they will make it in the next version.

achim~

>
>
> Pete
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] allowing configuration of builds?

[Pete Gavin]

On Mon, Feb 05, 2001 at 11:04:37PM +0100, Achim Gottinger wrote:
> 
> At the moment we focus on stability and do not want to add more features to
> ebuild.
> Once packages are all correct, secure and dependencies are all working we
> want to
> improve configuration.
> 
> Daniel is working on a next gen ebuild. I don't think such major
> modifications will be made
> to our current ebuild but they will make it in the next version.
> 

Oh, ok... Maybe I'm being a little to feature hungry :)

Oh, and I ran make check on the glibc build again, and it went fine this
time... The problem was the one you mentioned before. I wan't doing
anything other than compiling glibc, though, so I'm not sure what cause
the problem.

Pete

Re: [gentoo-dev] allowing configuration of builds?

[Achim Gottinger]

Pete Gavin wrote:

> On Mon, Feb 05, 2001 at 11:04:37PM +0100, Achim Gottinger wrote:
> >
> > At the moment we focus on stability and do not want to add more features to
> > ebuild.
> > Once packages are all correct, secure and dependencies are all working we
> > want to
> > improve configuration.
> >
> > Daniel is working on a next gen ebuild. I don't think such major
> > modifications will be made
> > to our current ebuild but they will make it in the next version.
> >
>
> Oh, ok... Maybe I'm being a little to feature hungry :)

:-) No problem we still think about new features for the next ebuild major
version.

>
>
> Oh, and I ran make check on the glibc build again, and it went fine this
> time... The problem was the one you mentioned before. I wan't doing
> anything other than compiling glibc, though, so I'm not sure what cause
> the problem.

This is definately a kernel/reiserfs problem. Take a look at the reiserfs
mailinglist and
watch out for low latency relatet mails.
What kerenle did you use 2.4.1-pre8 or 2.4.0-ac11 ?

achim~

>
>
> Pete
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] allowing configuration of builds?

[Pete Gavin]

On Mon, Feb 05, 2001 at 11:22:55PM +0100, Achim Gottinger wrote:
> >
> > Oh, and I ran make check on the glibc build again, and it went fine this
> > time... The problem was the one you mentioned before. I wan't doing
> > anything other than compiling glibc, though, so I'm not sure what cause
> > the problem.
> 
> This is definately a kernel/reiserfs problem. Take a look at the reiserfs
> mailinglist and
> watch out for low latency relatet mails.
> What kerenle did you use 2.4.1-pre8 or 2.4.0-ac11 ?
> 
> achim~
> 

I was using 2.4.1-pre8.

Pete

Re: [gentoo-dev] allowing configuration of builds?

[Achim Gottinger]

Pete Gavin wrote:

> On Mon, Feb 05, 2001 at 11:22:55PM +0100, Achim Gottinger wrote:
> > >
> > > Oh, and I ran make check on the glibc build again, and it went fine this
> > > time... The problem was the one you mentioned before. I wan't doing
> > > anything other than compiling glibc, though, so I'm not sure what cause
> > > the problem.
> >
> > This is definately a kernel/reiserfs problem. Take a look at the reiserfs
> > mailinglist and
> > watch out for low latency relatet mails.
> > What kerenle did you use 2.4.1-pre8 or 2.4.0-ac11 ?
> >
> > achim~
> >
>
> I was using 2.4.1-pre8.

So it is more definatly a kernel/reiserfs  problem. Things work better with
2.4.0-ac11.

What do you think about that temporary solution for the kernel configuration.

if [ "${LOPCAL_KERNEL_CONFIG}" == "interactive" ]
then
    make menuconfig
else
    if [ "${LOCAL_KERNEL_CONFIG}" ]
    then
        cp ${LOCAL_KERNEL_CONFIG} .config
     else
        cp ${FILESDIR}...../config .config
     fi
     yes "" | make oldconfig
fi

This way you can eigther pass your own config file or use the interactive
method.
If the var is not set it behaves as before.

achim

>
> Pete
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] allowing configuration of builds?

[Pete Gavin]

On Tue, Feb 06, 2001 at 12:06:19AM +0100, Achim Gottinger wrote:
> So it is more definatly a kernel/reiserfs  problem. Things work better with
> 2.4.0-ac11.
> 
> What do you think about that temporary solution for the kernel configuration.
> 
> if [ "${LOPCAL_KERNEL_CONFIG}" == "interactive" ]
> then
>     make menuconfig
> else
>     if [ "${LOCAL_KERNEL_CONFIG}" ]
>     then
>         cp ${LOCAL_KERNEL_CONFIG} .config
>      else
>         cp ${FILESDIR}...../config .config
>      fi
>      yes "" | make oldconfig
> fi
> 
> This way you can eigther pass your own config file or use the interactive
> method.
> If the var is not set it behaves as before.
> 
> achim
> 

Well, I've done a simple addition to the current ebuild script that will
set INTERACTIVE=y in the .ebuild file if it is passed w/ the -i switch.
I put it in sys-apps/portage/files/ebuild-pete. I'll also attach a
linux kernel ebuild script I put together to take advantage of this...

I'll email it to you separately from this message.

Pete

Re: [gentoo-dev] allowing configuration of builds?

[drobbins]

On Mon, Feb 05, 2001 at 04:38:15PM -0700, Pete Gavin wrote:

> Well, I've done a simple addition to the current ebuild script that will
> set INTERACTIVE=y in the .ebuild file if it is passed w/ the -i switch.
> I put it in sys-apps/portage/files/ebuild-pete. I'll also attach a
> linux kernel ebuild script I put together to take advantage of this...

OK; continue making your changes to ebuild-pete.  I'll need to think more
about the best way to handle an interactive compile process.

The way I upgrade to a new kernel is to first merge linux-sources.  Then
I cd to /usr/src/linux and make menuconfig and compile and install the
kernel by hand.  So for linux-sources, an interactive merge isn't needed.

The "linux" ebuild contains the default pre-compiled kernel for Gentoo Linux.
This kernel should be pre-configured by us to support the widest variety of
hardware configurations possible.  You shouldn't need an interactive compile
mode for this kernel.

I think we avoid this whole interactive compile problem if people who compile
their own kernels simply use linux-sources instead.  Which reminds me, I need
to fix the install guide again :)  I forgot to mention that the linux-sources
need to be merged first.

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.