To understand how fast you can create a new package, here is a quick guide.
Open Terminal and write:
mkdir -p ~/conary/foresight.rpath.org ~/conary/builds ~/conary/cache ~/conary/personal
cd conary
cd personal
cvc context personal
Now its done, created the “default folders” and a own personal folder. So now its time to remake opera package, lets say its a bit old and you want a newer today.
So lets go with opera.
Inside Terminal again, we are in folder /conary/personal/ and write:
cvc co opera:source=foresight.rpath.org@fl:2
It will create a opera folder inside personal folder. Everything for creating a “local” package is inside opera folder.
Lets go inside that folder with Terminal:
cd opera
If you like, you can open opera.recipe in gedit and edit the version nr to fit latest version. Now its time to cook it:
cvc cook opera.recipe
Lets wait few mins, until we can see:
Changeset written to: opera-10.00.ccs
Time to install it:
sudo conary update opera-10.00.ccs
Done, installed latest opera, built by yourself.
This is just a guide how to build a local package and install it, also getting a recipe thats already in Foresight repo.
Google Chrome 4.0.222.0
GNU/Linux x64yes, true. i forgot that it needs a context first. and the to folders gets created anyway.
My bad, thanks for pointing it out.
13:30
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090914 Foresight Linux/3.5 Firefox/3.5.3
I think it’s not strictly needed to create the ~/conary/builds and ~/conary/cache dirs; conary will create them silently. And if someone only wants to do a real quick package, ~/conary/foresight is not needed either.
And doesn’t one have to create the ‘personal’ context first, before ‘cvc context personal’?
Just my two cents; thanks for such a simple, clear guide