launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Nelson wrote:
> On Fri, Feb 5, 2010 at 3:58 PM, Aaron Bentley <aaron@xxxxxxxxxxxxx> wrote:
>>>> I thought the debian control directory specified the package name.
>>> Yes they do, hence the bug "Recipe requires sourcepackagename before upload"
>>> https://bugs.edge.launchpad.net/launchpad-code/+bug/515581
>> Okay, but doesn't that still contradict your statement that we can't
>> always know the package name from the branch?
> 
> Not that I'm aware of... when we create the SPRecipe, we need to
> supply a sourcepackagename, and at that point-in-time, the only
> guaranteed place where I can get that information is the changes file,
> which I *thought* I didn't have access to from LP (until it's uploaded
> after the recipe build succeeds). But let me know if I've
> mis-understood something.

We can always run things in scripts that do have access to the branches,
or we might be able to add something to the branch scanner that
identified package branches, including their sourcepackagename.

>>> It would be nice if the sourcepackage name wasn't required when a
>>> recipe is created, but as I understand it, the URL traversal that was
>>> previously decided on requires it:
>>>
>>> (code?) ~owner/distro/distroseries/sourcepackagename/recipename TheSo
>>> canonical traversal for displaying/editing a recipe.
>> There are probably ways we could get around it, e.g. by looking at the
>> contents of the package branch while creating the recipe.  Not sure
>> there's value in that.
> 
> Oh, I was under the impression that wasn't possible/allowed from an LP
> app server.

Not directly, no.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktsXD8ACgkQ0F+nu1YWqI0eOACeK3gn2YHWdbGr9ljKQyBFt01L
dAAAn2hqEQUH+IHuRLyDQkKkocNZz3ZH
=YfHY
-----END PGP SIGNATURE-----