Testing package imports locally

[John Arbash Meinel]

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

James Westby wrote:
> On Wed, 17 Feb 2010 11:57:00 -0600, John Arbash Meinel <john at arbash-meinel.com> wrote:
>> By the way, should this be split out into its own LP project? It
>> certainly isn't part of the bzr-builddeb codebase.
>> (bzr-builddeb-import-scripts ?)
> 
> It could be. It could be a new project, or under udd.
> 
> Aside from philosphical reasons, what would the benefits be?
> 
> I'm happy to do it if there is a justification, but having another place
> to check for merge proposals, bug reports, answers etc. would be a cost
> I would't want otherwise.
> 
> Thanks,
> 
> James
> 

Well #1, it gives a place to track bugs other than as bugs in
'bzr-builddeb'.

#2 the stacking code causes lp to stack on an unrelated branch
(bzr-builddeb). ATM it doesn't matter because the branches are small.
But it does mean it sets up stacking, and then goes ahead and pushes all
of the ancestry anyway.

#3 When submitting a merge proposal, it will pick the default 'trunk'
branch, rather than wanting me to merge into bzr-builddeb's trunk itself.

If I was picking a place, I'd pick udd, since that seems more a
'collection of random stuff', rather than a specific project. For now, I
guess one place is as good as another.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt8V8MACgkQJdeBCYSNAANajQCgvSjYs2fplJ8FzBRT5MPYAEO9
DYAAn2OALDQJ8PXL2BAv52eESNAoH2k0
=pcKt
-----END PGP SIGNATURE-----