[Debian-bootstrap] Listing binary packages with arch-specific names in dsc file

[P. J. McDermott]

On 2012-06-25 15:44, P. J. McDermott wrote:
> On 2012-06-25 13:50, Wookey wrote:
>> I'm still not sure this should go in source:build-essential, rather than a
>> new package called source:crossbuild-essential. This was discussed
>> in a thread starting here:
>> https://lists.debian.org/debian-devel/2012/01/msg00541.html
> 
> Well if it goes in src:build-essential, then it can use the existing
> (albeit rather complicated) packaging machinery.  This seems to work
> pretty well and keep things consistent.
> 
> Would a separate src:cross-build-essential be easier to maintain, not
> only due to potentially simpler (read: Autotools-less and Python-less)
> packaging, but also due to the ease of independently uploading new versions?

Actually, rereading the below ...

On 2012-06-24 08:05, Wookey wrote:
> +++ P. J. McDermott [2012-06-24 00:30 -0400]:
>> Might the crossbuild-essential-* packages be built from
>> src:build-essential? 
> 
> Yes, although I've actually proposed a similar separate source package
> for now, basde on the same code so that we can easily manage the
> toolchains outside the archive until they are actually uploaded to the
> archive, at which point merging source:build-essential and
> source:cross-build-essential should make sense.
> 
>> If there's time for it among the other work in
>> this project, I could work on that, as I'm familiar with how
>> src:build-essential generates its Depends field values for different
>> architectures.
> 
> OK. I started making a package from scratch then realised I should
> base it on build-essential and got as far as downloading the source.
> I'm assuming it's actually about a 2-hr job if I got my finger out.
> Feel free to beat me to it :-)

... I've realized you just mean forking src:build-essential to use the
same packaging machinery and just build crossbuild-essential-<target>
packages.  I've pretty much done that, except my "fork" is still called
src:build-essential and still builds a binary package named
"build-essential" (but only if the binary-arch target of debian/rules is
used). :)

So I can rename the source package and remove the build-essential binary
package, resulting in a src:cross-build-essential package that can, at
least temporarily, exist in the archive alongside src:build-essential,
with the option of someday rather painlessly merging the two source
packages (i.e. renaming src:cross-build-essential to src:build-essential
and re-enabling the building of build-essential from it).

-- 
P. J. McDermott                                        (_/@\_)    ,--.
http://www.pehjota.net/                           o    < o o >   / oo \
http://www.pehjota.net/contact.html                 o   \ `-/    | <> |.
                                                o o o    "~v    /_\--/_/