Go to the FreeLists Home Page Home Signup Help Login
 



[openbeos] || [Date Prev] [12-2001 Date Index] [Date Next] || [Thread Prev] [12-2001 Thread Index] [Thread Next]

[openbeos] Re: Package Management System.

  • From: "Travis Smith" <sage@xxxxxxxx>
  • To: <openbeos@xxxxxxxxxxxxx>
  • Date: Wed, 5 Dec 2001 13:08:49 -0500
<snip>
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?
</snip>

One thing I was considering is that you also merge all of the xml files
together as you download them. I honestly don't know if this is as good
as it could be. I haven't touched xml before, so I only know the little
I've read.

<snip>
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?
</snip> 

I see no reason why it wouldn't. And I was thinking it would require
something like that. The xml file... Umm... Fields is the correct word?
The fields haven't been decide upon, so the exactly specs of the file
isn't know yet. 






[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.