On Sunday 07 September 2003 13:51, Joshua Banks wrote: > Good question.. :) > > I was kindof wondering the same thing. What if I want to install > something in tar.gz format that isn't in the portage tree? Will > gentoo still let us compile source manually via ./configure, make, > make install commands or not? Or are the commands different?
Before doing your own ebuild you should really search the gentoo bugzilla if somebody has allready made an ebuild for that particular software. If not then follow the next one. Simply copy the /usr/portage/skel.ebuild to your local portage tree to the category of your choice (well inside a directory of the name of the package you want to use) and rename it to <package-name>-<version>.ebuild Fill the required variables in that ebuild and save. ebuild relative/path/to/your/ebuild digest This will fetch the tarball from what ever source URI you set in the ebuild and create the digest and manifest files. Then simply emerge your-package. If it bails out try the alternative methods in compile and install functions in the ebuild you filled up. The skel.ebuild is heavily commented so it's quite self explanatory. After it compiles and works (Like most software will) you can contribute to Gentoo and fill an ebuild addition bug for that software to be added in portage official tree. Before makeing the bug report strip all the skel explanation comments from the ebuild and double check that it still compiles okay and submit. I allways try to do that if I get software that is not in portage tree. PS. Read the softwares home page to see what that software requires as dependencies and fill those packages to the DEPEND in the ebuild. PS. PS. if that package should use some USE flags to make the compilation conditional and you don't get those right then at least mention these things in the bug report, so that the person who handles your bug report don't need to find that out later, but knows that your ebuild is not a complete solution. -- [EMAIL PROTECTED] mailing list
