From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_12_24, DMARC_MISSING,FREEMAIL_FROM,FROM_LOCAL_DIGITS,FROM_LOCAL_HEX, FROM_STARTS_WITH_NUMS,INVALID_DATE,MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=no autolearn_force=no version=4.0.0 Received: from mailout02.sul.t-online.com ([194.25.134.17]) by cvs.gentoo.org with esmtp (Exim 3.22 #1) id 14Pto3-0003V8-00 for gentoo-dev@gentoo.org; Mon, 05 Feb 2001 15:08:20 -0700 Received: from fwd00.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14PtoO-0006QM-01; Mon, 05 Feb 2001 23:08:40 +0100 Received: from helios.bagwan (320095285153-0001@[217.80.39.140]) by fwd00.sul.t-online.com with smtp id 14PtoK-1nHa8OC; Mon, 5 Feb 2001 23:08:36 +0100 Received: (qmail 14932 invoked by uid 0); 6 Feb 2001 00:49:48 -0000 Received: from sadchitananda2.bagwan (HELO gottinger.de) (achim@192.168.2.1) by helios.bagwan with SMTP; 6 Feb 2001 00:49:48 -0000 Message-ID: <3A7F1E40.FA4D7C75@gottinger.de> From: 320095285153-0001@t-online.de (Achim Gottinger) X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] interactive packages? References: <20010205070043.A10444@cvs.gentoo.org> <3A7EB2BA.6DD6E242@gottinger.de> <20010205131802.A26227@alkaline.anarchy> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 320095285153-0001@t-dialin.net Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@gentoo.org X-Reply-To: achim@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Mon Feb 5 15:09:02 2001 X-Original-Date: Mon, 05 Feb 2001 22:42:25 +0100 X-Archives-Salt: 5879b28a-bf3a-43e4-b2cd-1aa8e0aa8573 X-Archives-Hash: ed13957c27b774160d2b286f64f47bad pbg1854@garnet.acns.fsu.edu wrote: > Ok... > > How about we make an option to ebuild that makes the build process > interactive. We could make that option set a variable in the ebuild > script, which we would then check during the individual steps in the > process.. for example, > > if [ "${INTERACTIVE}" ]; then > make menuconfig > else > cp "${FILESDIR}/config-${KV}" ${WORKDIR}/linux/.config > yes "" | make oldconfig > fi Thats what I ment by the USE variable method. > > Then you could run ebuild -i merge or something like that. > We do not use flags for ebuild at the moment. Maybe in future > > A few notes: > I like using make oldconfig, because it automatically takes care of > autoconf.h, and version.h for you, and makes sure everything is > configured right. I'd use yes "" | make oldconfig in the > non-interactive version, that way if there are any variables missing > in the .config file, they will get the default value. That sounds good. I think I saw that option last week in some magazine. > > > I also thought it would be a good idea if the kernels were installed > with a suffix determining the version of the kernel, > i.e. bzImage-2.4.0 rather than just bzImage; that way multiple kernels > can be installed at the same time. I like to do this, especially when > installing a new kernel, in case the new one won't boot or has some > kind of bug in it, I can go back to the old one. Then you could merge > the new kernel, reboot, and unmerge the old one after you're satisfied > the new one works. But what if you configure manual and have different kernels of the same version? > > > If you want, I'll try to modify the ebuild script to add interactive > building support, and work on a sample kernel ebuild. Adding > interactive support shouldn't require any modifications in the > packages, I'm pretty sure. > > Oh... and one more thing... I'm having problems w/ the make check > stage while building glibc-2.2.1. I'm trying to figure out why right > now. It just says "Timed out" or something like that. I'll give you > more info after I run make check again. Hmm, sounds like LFS <-> low latency problem. I saw that over here once but at that time I had a lot of parallel build processes running. > > achim~ > > Pete > > On Mon, Feb 05, 2001 at 03:03:38PM +0100, Achim Gottinger wrote: > > Pete Gavin wrote: > > > > > Hi, > > > > > > I was wondering... Is it required that an ebuild script be completely > > > non-interactive? > > > > Yes, otherwise there would be no autobuild. > > > > > I have a few ideas for the kernel configuration > > > scripts. I think it might be cool for the for the ebuild to ask the > > > installer if he/she wants to load a .config file from somewhere else, then > > > run make menuconfig. That way all the modules and stuff can be removed > > > with portage-unmerge. > > > > You can do this. > > After running "ebuild linux.... unpack" cd to > > /tmp/portage/linux.../work/linux > > run "make menuconfig/xconfig" > > Then continue with ebuild linux... compile > > > > Another possibility would be using the "config" function in ebuild. This was > > normaly intedet to be used > > for an opional additional configuration-layer. And should normaly modify the > > package configuration > > files from templates/databses whatever. Normaly this functions hsould be > > called after pkg_merge. > > But since we have no configuration layer right now and config is only used by > > a few packages (for example > > qmail runs config-fast from within the config function) we could use the > > config function for such an > > interactive thing. > > Another solution could be using a USE variable to decide if the manual > > configuration you described should be > > run or a variable that just triggers if a private config file should be used > > instead of the default one. Or we could make a sepearate kernel package that > > does these manual steps. > > > > But what do you think about that. The kernel ebuild looks if a file (for > > example /etc/kernel/[version].config) exists. If so it uses this instead of > > the default one. > > If you want to configure the kernel for the first time you can do it as I > > described above. The copy the .config file to /etc/kernel/[version].config > > and the next time you compile the kernel your private config file gets used. > > > > achim~ > > > > > > > > Pete > > > > > > _______________________________________________ > > > gentoo-dev mailing list > > > gentoo-dev@gentoo.org > > > http://www.gentoo.org/mailman/listinfo/gentoo-dev > > > > > > _______________________________________________ > > gentoo-dev mailing list > > gentoo-dev@gentoo.org > > http://www.gentoo.org/mailman/listinfo/gentoo-dev > > _______________________________________________ > gentoo-dev mailing list > gentoo-dev@gentoo.org > http://www.gentoo.org/mailman/listinfo/gentoo-dev