change a package to become a dependency of another

jerryluc · 2008-10-23 08:02:18

i was wondering if i could change a package to be a dependency, Well, i know i could use abs to change PKGBUILD.

But yesterday gnome was upgraded on my machine, and i got an error with a package. I suspected it was because gnome was running, and was a little bit quick just to kill X and install the package explicit. Now i didn't get any error messages, but the package was no longer a dependency of gnome. Could i change that one package to become a dependency of gnome once again?

klixon · 2008-10-23 08:58:16

pacman -Rd ${PACKAGE} && pacman -S --asdeps ${PACKAGE}

Should work, I think

jerryluc · 2008-10-23 18:20:57

thanks, pacman <3

bender02 · 2008-10-23 19:37:49

Just a language remark: the package would still be 'a dependency'; the thing that changes is that it's not marked as 'installed as a dependency'.

Xyne · 2008-10-23 19:43:03

klixon's advice will mark the package as a dependency, but the only way to make it a dependency of gnome (so that it gets installed and uninstalled with it) would be to change the database desc file, which is really impractical. Without that, pacman will consider the package an orphan, so be careful when you clean out orphans.

bender02 · 2008-10-23 22:39:42

Xyne wrote:

klixon's advice will mark the package as a dependency, but ...

As far as I understood the first three posts, that was exactly the point. That's why I posted the 'language remark', since I gathered that OP wanted to 'have the reason to be installed as a dependency' and not really change the dependency list of anything. But again, maybe I'm wrong.

Xyne · 2008-10-23 22:50:38

bender02 wrote:

As far as I understood the first three posts, that was exactly the point. That's why I posted the 'language remark', since I gathered that OP wanted to 'have the reason to be installed as a dependency' and not really change the dependency list of anything. But again, maybe I'm wrong.

I interpreted the thread's title and the last line of his post to mean that he wanted it to be handled as if it were a true dependency of gnome (as he claims it used to be):

jerryluc wrote:

Could i change that one package to become a dependency of gnome once again?

Only the OP really knows what he wanted though (and maybe not even him, depending on how philosophical you want to get ).

Arch Linux

#1 2008-10-23 08:02:18

change a package to become a dependency of another

#2 2008-10-23 08:58:16

Re: change a package to become a dependency of another

#3 2008-10-23 18:20:57

Re: change a package to become a dependency of another

#4 2008-10-23 19:37:49

Re: change a package to become a dependency of another

#5 2008-10-23 19:43:03

Re: change a package to become a dependency of another

#6 2008-10-23 22:39:42

Re: change a package to become a dependency of another

#7 2008-10-23 22:50:38

Re: change a package to become a dependency of another

Board footer