On Thu, Nov 19, 2009 at 9:36 AM, Julian Edwards <[email protected]> wrote: > Michael Hudson wrote: >>> However, my second point still stands. We need to traverse to a recipe >>> before the source package exists. >> >> I don't really get this. It sounds like the model poking the UI in the >> eye. (If we really have to, we can have the appropriate traverse() >> method look ahead in the request and do different things if the next but >> one segment is "+recipe"). > > Well let's put it another way - you have a new recipe for a new package > that's not in Launchpad. > > How would you traverse to it? It seems a bit chicken-and-egg to me. > >>> Another thing to consider is the owner. Do we want to make that part of >>> the key data you need to resolve a single recipe? >> >> I don't know (honestly). It would make the URLs even longer, but would >> probably be more consistent with the rest of Launchpad. > > Yeah that was my worry. > > Jono, any opinion? >
I haven't kept up with this thread so far. My own opinion is that the exact details of traversal don't matter yet, just as long as we pick something that allows: * recipes to refer to one another. * finding all of the recipes that are associated with a given source package * finding all of the recipes that are associated with a given branch * linking to past builds of recipes * creating recipes for things (esp. SPNs) that don't exist yet. There are many traversal paths that satisfy all of these constraints. https://launchpad.net/+recipe/$RECIPE_ID being the simplest. The open questions we have, as I see it, are: * should recipes have names? (probably yes) * what should be the namespaces? In that case, I wonder what's the simplest thing that could possibly work. Perhaps I should read the thread :) jml _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
