package dependancy issues

[GoogleCodeExporter]

You add a package dependancy but not remove it.

This is noticeable when you have a package with 0 deps, add a single dep 
then attempt to remove.

version: wpkgexpress_v1.0-r5.tar.gz

Original issue reported on code.google.com by mem.name...@gmail.com on 8 Oct 2009 at 7:13

[GoogleCodeExporter]

just tested on wpkgexpress_v1.0-r6
The issue is still present.

Original comment by mem.name...@gmail.com on 8 Oct 2009 at 8:22

[GoogleCodeExporter]

Also related to this bug:

You cannot delete a package that has another package depending on it.

eg:

* Package1 deps on Package2
* attempt to delete Package1
* frontend confirms deletion but package1 is not deleted.

Original comment by mem.name...@gmail.com on 8 Oct 2009 at 8:27

[GoogleCodeExporter]

I have answered these issues over on the discussion forums here:
http://groups.google.com/group/wpkgexpress-support/browse_thread/thread/7a90aa34
ad641845

The short version is: dependencies can be removed by using the ctrl+click 
method, and
the "issue" of being unable to delete packages that are depended on by other
packages, has been by design since the beginning.

The reason for this latter "issue" is that if any number of other packages 
cannot
function properly without a certain package (in other words, it's dependent), 
it does
not make sense to allow that certain package to be removed if others are still
relying on that package existing. This is why to aid in removing such 
dependencies to
be able to remove the package in question, I made clickable links to the 
dependent
packages in the error message as well as in the "depended on by" packages list 
in the
details view of each package that may have packages dependent on it.

Original comment by msc...@gmail.com on 9 Oct 2009 at 1:12

[GoogleCodeExporter]

Original comment by msc...@gmail.com on 26 Oct 2009 at 2:27

• Changed state: Invalid