You got it right that loadRecipe needs the name of the package. But to access information from the recipe, you should use the class defined there, not the package name or the recipe filename. (That's also quite natural.
Sometimes recipes can define more than one classes. ) For example, in a firefox plugin, I want the version of firefox, so that the plugin can be installed to the right place loadRecipe('firefox') class FirefoxPackageSearch(PackageRecipe): snip def setup(r): snip r.macros. Ff_version = '.'.
Join(FireFox.version. Split('.'):2) I load the firefox recipe and use Firefox. Version to get what I want.
You got it right that loadRecipe needs the name of the package. But to access information from the recipe, you should use the class defined there, not the package name or the recipe filename. (That's also quite natural.
Sometimes recipes can define more than one classes. ) For example, in a firefox plugin, I want the version of firefox, so that the plugin can be installed to the right place. LoadRecipe('firefox') class FirefoxPackageSearch(PackageRecipe): snip def setup(r): snip r.macros.
Ff_version = '. '. Join(FireFox.version.
Split('. '):2) I load the firefox recipe and use Firefox. Version to get what I want.
Since conary is just like (almost) coding in python: p = . Version print 'your package's Version Number: ' + p rhs = p. Split("_",1) print 'Latest Your Package's Changeset: ' + rhs1.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.