All right. Now I understand what we are talking about :-) I Will still have a look into the Documentation. You never can know too much :-)
Am Freitag, 26. August 2005 01:36 schrieb Holly Bostick: > Markus Döbele schreef: > > Okay. Understood! > > I would like to have a look in how an ebuild is constructed. > > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=6 > > This is the English version; if you would prefer to read it in German: > > http://www.gentoo.org/doc/de/handbook/handbook-x86.xml?part=3&chap=6 > > Unfortunately, this section of the developers handbook appears to be > only available in English: > > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 > > > I figured out how to create an rpm and now want to know how it looks like > > for an ebuild. > > I think you perhaps misunderstand what an ebuild is. It's not an > 'application', it's a text file (script, actually) that instructs the > system how to compile the application in the most common case of > installing from source tarballs. The vast majority of programs on a > Gentoo system are compiled from source, such compilation being > customized for the individual system via the use of USE flags, which the > user specifies at the time of compilation. The USE flags, generally > speaking, conform to ./configure options that you might be more familar > with, and the ebuild is basically a mediator between the human > understanding of USE flags such as +gnome or -kde and the compiler's > understanding of --enable-gnome-support and --without-kde. > > In the case of the relatively few binary applications that can be > installed via Portage, the ebuild mostly contains extraction > instructions (since a binary isn't going to be compiled, but just copied > to the appropriate place in the filetree so that the user knows where > it's likely to be), and sometimes whatever 'einfo' messages the user > might want to see/know (special notes about configuring or running the > installed program. > > But you've already done all the work needed, insofar as you've got a > working binary. So you don't have to 'create' anything else other than a > way for Gentoo users to connect to the binary with our automated package > manager, Portage-- which is what the whole issue over moving the files > to Sourceforge is about. > > Since we know Nick's ebuild works, from the testers, Nick, why don't you > just send him a copy? > > It is GPL, isn't it ;) ? > > Holly -- gentoo-user@gentoo.org mailing list
