Muharem Hrnjadovic wrote: > Michael Hudson wrote: [..] >> Let's start with a recipe. In the abstract, a recipe is roughly a thing >> that specifies how to combine branches into something that debuild could >> turn into a source package -- a "debianized source tree". Recipes today >> are specified as text files that the 'bzr-builder' plugin parses and >> acts on. An obvious open question in choosing how to represent these is >> either to store them in a parsed form, with all the structure of a >> recipe in the schema or unparsed, as lumps of text. >> >> Or, and there are actually reasons for doing this, we could do something >> in between: store it mostly as text but replace the references to >> branches in the text with references to database objects (probably the >> id of entries in some RecipeBranch linking table). This would let us >> (a) check that the branches exist at parsing time (b) keep the >> references up to date if the branch is moved or renamed (c) prevent >> branches that are referenced in Recipes from being deleted. > I like this. How would we reference the linking table rows in the recipe > text? Please ignore my question, I just re-read your email and saw this:
[..] >> - recipe >> - a text field containing the text of the recipe (probably with >> mangled branch references so lp:foo would be replaced with lp:21435) [..] Best regards -- Muharem Hrnjadovic <[email protected]> Public key id : B2BBFCFC Key fingerprint : A5A3 CC67 2B87 D641 103F 5602 219F 6B60 B2BB FCFC
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
