make an ebuild emerge deps, even if its already emerged

Message

Duck-Billed Platypus · Sat Feb 26, 2005 12:58 am

is it possible to make an ebuild emerge a dep, even if it's already emerged?

hds · Post by **hds** » Sat Feb 26, 2005 1:33 am

Duck-Billed Platypus wrote:is it possible to make an ebuild emerge a dep, even if it's already emerged?

not that i would know, but why dont you simply re-emerge the dependancy in that case?
i guess you like to re-emerge a lib? perhaps you give us an example..

Duck-Billed Platypus · Sat Feb 26, 2005 1:36 am

its the first time im making an ebuild. im trying to make a meta-ebuild for the enlightenment foundation libraries. they're all cvs, so you need to re-emerge the packages in order to update it.

hds · Post by **hds** » Sat Feb 26, 2005 1:43 am

but if you update the packages from cvs, this is not a re-emerge, but a different version? hmm.. you what have to make ebuilds of those as well in that case, and call them "lib-whatever-cvs". (not sure if i understood you correctly, though..)
you say that you want to install a lib, which has already been in portage, but not as a cvs version, right?

Duck-Billed Platypus · Sat Feb 26, 2005 2:14 am

theyre all in portage, but they get source from cvs. ie imlib2-9999, its always that version.

hds · Post by **hds** » Sat Feb 26, 2005 8:48 am

Duck-Billed Platypus wrote:theyre all in portage, but they get source from cvs. ie imlib2-9999, its always that version.

well, in this case, your ebuild could simply emerge imlib2-9999 (example from your case) everytime, regardles if it was already installed or not? i mean, this is actually what you want, so why would you want to check if it is already there?

rhill · Post by **rhill** » Sun Feb 27, 2005 8:04 am

short answer: no. but a bash script works nicely. ;d

make an ebuild emerge deps, even if its already emerged

make an ebuild emerge deps, even if its already emerged

Re: make an ebuild emerge deps, even if its already emerged