libapt-front introduction

[14:41] <enrico> The other problem is that all libapt-front code will give you aptFront::entity::Tag objects for tags
[14:42] <enrico> but we can probably hack this HandleMaker to make it transparent for you
[14:42] <enrico> So, some intro in libapt-front
[14:42] <enrico> its main concepts are Cache and Entity
[14:42] <enrico> Cache is the place where Entities come from
[14:43] <enrico> sorry, Component and Entity, and Component is the place where Entities come from
[14:44] <enrico> examples of Components are Packages, Tags and PackageTags
[14:44] <enrico> examples of Entities are Package, Version, Tag and Facet
[14:44] <enrico> There's some more than that, but it gives the idea

you can gdb it and set a breakpoint on __cxa_throw, to see where the exception is actually thrown
"break __cxa_throw"

# to generate the release version use "CONFIG += my_release" as arguemnt for qmake on
# the command line - this was neccessary because "release" is declared
# by default - so it must be removed manually using "CONFIG -= release"
# however using kdevelop this is not possible so I've created this workaround


libtagcoll
	

tagcoll
	Vocabulary - can read the tag database including the implications and description, it maps the 
		tags to the associated data
	
Open questions for libapt-front

How to update the database?
	- is it simply aptFront::cache::Cache.reopen()?
	- will anybody be notified?
	- what are the observers observing?
	- what does aptFront::cache::component::Packages::packageByName return if there is no 
	  such package?
	  
	getCompanionTags : shouldn't it contain the tag itself?