Bjorn Tillenius wrote: > On Thu, Oct 29, 2009 at 02:44:40PM +0100, Muharem Hrnjadovic wrote: >> Hello Bjoern, >> >> the URIs we currently use for package sets are like >> >> '../package-sets/mozilla' >> >> Because package set names are only unique in combination with a distro >> series now the URIs will need to change to something like: >> >> '../package-sets/karmic/mozilla' >> >> or >> >> '../package-sets/mozilla/karmic' > > Let's wait to discuss the implementation details. I'm a bit interested > in how a URL for a package set looks like. You said on IRC that you
With the database schema changes that already landed on db-devel package set names cease to be unique globally i.e. a package set names are now only unique in combination with a distro series. That breaks the existing package set naming/traversal scheme. > decided to give package sets it's own top-level space. And looking at > the code, a URL path looks like: > > /package-set/desktop > > And with a distro series, it would be either > > /package-set/desktop/hoary > > or > > /package-set/hoary/desktop In order to fix the currently broken traversal scheme for package sets and have a working LP API after the roll-out on 04-Nov-2009 I will need to land a branch that adopts the URI structure above (e.g. /package-sets/karmic/kernel-packages) today. Having said that, I am wide open to discussing package set URI/traversal changes for the forthcoming LP developement cycle. > Now, the obvious question is, what about the distribution? Are we not > going to have package sets for non-Ubuntu distributions ever? Why Good question. I understand we'll be only using them for Ubuntu in the immediate future but may well decide to use package sets for other distributions at some later point in time. > doesn't the package set hang of the distribution in the first place? This is an interesting question and reminds me of a question Curtis H. brought up yesterday. What happens in a case where we have 2 distributions A and B with an identically named distro series X and both requiring a package set named 'kernel-packages'? In such a case our current package set naming/traversal scheme would not hold up. > Given the current URL structure, how will the UI navigation look like? Another good question. The emphasis so far was on providing package sets (and archive permissions based on them) via the LP API in order to facilitate the distro team's archive re-organisation effort. Maybe Michael N. can comment on this..? 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
