Talk:Writing Ebuilds

Thank you for this succinct beginner's guide.

Someone else stuck that line above, and I appreciate gratitude! I am thakful as well, and here below I am therefore trying to comtribute myself

An ebuild example
I've just added my (not mine, I mean, but I added it, what an achievement!)... my first ebuild to my portage tree, thanks to this guide, and I'd like to propose it as an example, and only link here from the main text.

frandom-1.1.ebuild, the unsigned ebuild
Only on can it be found at this time:

New package: frandom (to sys-apps?) 

The ebuild itself is here: 

It's an unsigned ebuild AFAIK. Meaning, I guess, that it isn't anywhere in any publicly accessible overlay to be emerged from. At least not yet, or at least not that I was able to find it.

It is a great package containing   which you want to use if you want to do encrypted partitions of not small size. It randomized my LVM2 raid5 1.7TiB partition within only about seven (7) hours, and it would have taken me probably 70 hours with.

Pls. look up this procedure which I am currently following: Root_filesystem_over_LVM2,_DM-Crypt_and_RAID

There I got the recommendation for it. It is true, the frandom is fast and furious in comparison.

As the guide to which I attach this talk says,

create:

a directory for your ebuilds, that is your own overlay. That's where we'll be adding our ebuilds!

Now add this line to Gentoo's principal configuration file.

That will make emerge knowledgeable about yer overlay and them ebuilds!

which is the exact structure needed.

Download the ebuild and save it as:

So far so good... Now copy some other minimalistic and which you can browse galore at

and accomodate the contents thereof for our sys-apps/frandom private ebuild of our own making (I sure mean just the placing of it under the nose of the emerge, credit goes to the respective Joel the no-surname Developer et alia, as linked to at the top!).

The accomodation to the aforesaid two files (there'll be just one more to get calculated also) to add in our directory created in our overlay, the minimalistic one which I made can be seen:


 * 
 * 

And has to be made by gentoo utilities in you box.

With that command above. And that command once it downloads and checks the archive (read the ebuild itself, there the command gets the instructions from), places the file in the directory of ours.

Now you can run

and emerge will install the frandom.ko for you (frandom, and erandom the companion of his, is a module. I don't remember at this time (time for bed here, and work aplenty still ahead to get my Root_filesystem_over_LVM2,_DM-Crypt_and_RAID for me), I don't remember if there were any more requirements. Just, when I issued: (which sure is just a variant I use of the same), it installed the brand new shiny:

first, and then the frandom package itself (I sure did as well, where "2" was in my case, pointing at the new kernel). Actually it failed, because the kernel needs to be compiled first. But, when I compile it, and emerge frandom, upon reboot, I'll be able to just:

and be able to use, as I already did, just this time for a another Gentoo system the instructions as per Root_filesystem_over_LVM2,_DM-Crypt_and_RAID. Anyway, read the source and ddg.gg or ixquick  for more (To torch you need to get deeper into hidden services. Pls. don't misunderstand me, I don't mean anything illegal or wrong, I only mean privacy, and my own and your own freedom from surveillance!... torch is the hidden search engine)... I recommended those because Google is a global spy, not anymore faithful to its original ideas. And I will add the question to you: Will our GNU Linux go that reprobate road as well? Read on the forums whether Linux is in danger of going surveillance ready! Here: !