From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from acme.geekasylum.org (acme.geekasylum.org [203.30.145.10]) by chiba.3jane.net (Postfix) with ESMTP id E127CAC9B5 for ; Wed, 17 Apr 2002 07:08:15 -0500 (CDT) Received: from buffy (buffy.geekasylum.org [203.30.145.20]) by acme.geekasylum.org (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with SMTP id g3HC8Dq10125 for ; Wed, 17 Apr 2002 22:08:13 +1000 From: "Todd Wright" To: Subject: RE: Good ebuild examples to learn from - Was Re:[gentoo-dev] ebuild question Date: Wed, 17 Apr 2002 22:08:15 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20020417113821.GA2352@pasokan.laua.cibsnet.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 1c9cd93d-58bc-449c-9b9c-b469c587901b X-Archives-Hash: 282f06f65d80df11791306e0efa76852 > > Pichai Asokan wrote: > > >Can some of the developers take a few minutes to suggest > > >the ebuilds to study for 'would be contributors'? > >=20 > > Without being specific I'd say look at ones for software you have=20 > > compiled on your own from the source in the past, that way you'll be = > > familar with what should be going on. > Thanks; > but often it was a case of=20 > (un)tar > ./configure > make > make install > Well; I could have looked at what went where, but I never did :-( > So I am not sure how much this will help. > P Asokan Pichai, It will help, as I said in my email to you off-list, looking at other = ebuilds is a great way to learn how to write them. In fact you will see = that usually, what a lot of ebuilds do is (un)tar ./configure make make install Not too difficult, huh? Its pretty familiar. What you need to look at = is mainly how the ebuild optionally includes (or excludes) for example, = ssl support by checking the use flags and then adding the appropriate = option to the ./configure parms You dont need to know what goes where. Portage builds everything in a = sandbox. The 'make install' part should install everything to the = 'image' dir (under /var/tmp/portage). Sometimes it needs = special attention to achieve this. You may have seen people complain = about ACCESS DENIED errors - you get these if 'make install' trys to put = things outside of this 'secured' directory, so you will see ebuilds that = say 'make DESTDIR=3D${D} install' to ensure everything is installed into = the sandbox. Later the src_install() function of the ebuild moves everything to its = proper and final place on the system. Thats probably the most compex = part of putting tother an ebuild, and once youve done it a couple of = times, its not so tough. Anyway, sounds like you're on your way. Feel free to bug me again if you = need any help. -- _--_|\ --------- Todd Wright -- wylie@geekasylum.org -------- / \ =20 \_.--._* <--- http://www.dreams.darker.net/~wylie/ v Mobile: +61-403-796-001 Ph: +61-2-9521-8677 ----------------------------------------------------------------