[openbeos] Re: Package Management System.
- From: Dan Sinclair <dj2sincl@xxxxxxxxxxxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 5 Dec 2001 12:51:57 -0500 (EST)
Hey,
> The you will know the package dependences when you remove the package,
> so I don't see it an issue to check to see if any other installed
> package requires that dependency, and if not ask to remove it.
The only problem I see with scanning the other .xml files it it chould
take a long time, order the nubmer of installed packages. Which is why I
thought a Dependants section might be helpful, lists everything that needs
this package to run. If there are no Dependants then you can remove the
package? Or am I just making more work?
> Does that answer everything you were asking?
I think so. But I got a new one, in the dependancies section is there a
way to say which version, aka if i have a package that requires > v5 of
some library can I state that, or if I need < v5 could I also say that?
For instance if the developer radically changed an API and we use only the
older/newer version at the moment?
I guess that could easily to do something like debians dist-upgrade
just list everymajor component in the dependancies section of the main
file and let it go.
dan
- Follow-Ups:
- [openbeos] Re: Package Management System.
- From: Travis Smith
- References:
- [openbeos] Re: Package Management System.
- From: Travis Smith
Other related posts:
- » [openbeos] Package Management System.
- » [openbeos] Re: Package Management System.
- » [openbeos] Re: Package Management System.
- » [openbeos] Re: Package Management System.
- » [openbeos] Re: Package Management System.
- » [openbeos] Re: Package Management System.
- » [openbeos] Re: Package Management System.
- [openbeos] Re: Package Management System.
- From: Travis Smith
- [openbeos] Re: Package Management System.
- From: Travis Smith