[indiana-discuss] pkg uninstall without deps

[Alan Coopersmith]

Shawn Walker wrote:
> Alan Coopersmith wrote:
>> Shawn Walker wrote:
>>> Alan Coopersmith wrote:
>>>> Unfortunately, besides having to figure out how to parse the output of
>>>> pkg uninstall -rnv, it would have to be fixed first to not throw a
>>>> traceback:
>>> The error you're seeing is an out of memory one.  What sort of system
>>> are you running this on (how much memory, etc.)?
>>
>> Ultra 40, 1Gb RAM.   Fresh installed 2008.11 RC2, then did a
>> pkg install redistributable, so 'pkg list | wc -l' shows 1190 packages.
> 
> That shouldn't happen :(
> 
> Can you file a bug if you can reproduce it again along with your
> cfg_cache, and the output of pkg list attached?

I reclaimed some memory by killing very large (150Mb+) updatemanager &
firefox processes and tried again and it still happened.  Submitted as:
http://defect.opensolaris.org/bz/show_bug.cgi?id=5832

>>> Also, why would you need to parse the output?
>>
>> How else does the script know what packages to reinstall afterwards
>> so that upgrade-X doesn't leave the system without GNOME, Java, etc?
> 
> Ah, I was assuming that you would rely on the dependencies to reinstall
> these.

On what dependencies?   I can't just install every package that depends
on libX11 - that will probably include hundreds of new packages that weren't
previous installed.   I can run 'pkg contents -o pkg.name,action.raw -t depend'
and parse that output and do my own recursive descent, but I thought you were
suggesting I could use pkg uninstall -rvn to do the recursive descent and
produce that list for me.

>> (The other problem with the "migrate to custom IPS repos" plan is that right
>>  now I can tar up all our SVR4 packages and put them on the opensolaris
>>  download center for people to test - until someone sets up a
>>  pkg.opensolaris.org/project/ namespace or something similar for opensolaris
>>  projects to host their own packages on a public repo, I can only use SVR4
>>  packages to make test builds available to the community.)
> 
> Maybe we need an /alpha repository in addition to the /dev repository? 

Except we need them for each project, because in my world, the SUNWxorg-server
package you download from the vconsoles project will be different than the one
I'm putting out for the Xorg-1.5 upgrade project.   In the ON world, I expect
it's more like dozens of projects under parallel development, and you'd want
different bits from the Crossbow, ZFS-Crypto, etc. builds, which may have
the same version number and timestamps that make one look like a newer build
of the other when it's not.

It'd be especially nice if I could have my pkg.opensolaris.org/projects/xorg-1.5
repo be a "overlay" of pkg.opensolaris.org/devel, with only the dozen packages
I need to replace in it, and all dependencies and other packages pulled from the
main one, but even just a simple repo management webapp (similar to the SCM
management webapp being rolled out for projects) that let me set up a new
project repo by cloning /devel and then pkgsend'ing the changed packages would
be awesome.

-- 
	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering