public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: andrew@ncrmnt.org
To: "Chris Packham" <Chris.Packham@alliedtelesis.co.nz>,
	bryanhundven@gmail.com, crossgcc@sourceware.org,
	"John Collis" <John.Collis@alliedtelesis.co.nz>
Subject: Re: crosstool-NG Debian packaging
Date: Wed, 10 Feb 2016 21:43:00 -0000	[thread overview]
Message-ID: <4313479a694e9b4b91d7842dc4e3c690@cloud.ncrmnt.org> (raw)
In-Reply-To: <ae340ee12b524a9ab83d420b8f5cf8ca@svr-chch-ex1.atlnz.lc>

10 февраля 2016 г., 23:32, "Chris Packham" <Chris.Packham@alliedtelesis.co.nz> написал:
> Hi Bryan, Andrew,
> 
> I see that there is some movement on packaging crosstool-NG for Debian. 
> This is relevant to my interests and I have subscribed to your mailing 
> list :).
> 
> Is there an open Debian bug for this? I've found a few older ones but 
> they all seem to have timed out due to lack of interest.

Hi, Chris. Unfortunately, I'm not a debian maintainer and there's no open bug 
for that in debian bugtracker. I've done the packaging for my own needs, 
since it was waaay faster than opening a bug ;). So unless you know some debian 
maintainers crosstool-ng won't land in debian repositories any time soon;) 

> I'm also interested in the possibility of generating debian packages for 
> the toolchains themselves.
> 
> We're in the process of updating our cross toolchain(s) and being able 
> to distribute .deb files to our developers is quite attractive. Is 
> anyone looking at such a capability? If not any pointers?

I guess the simplest way would be generating a static toolchain tarball and later 
writing an independant wrapper that would generate a deb and place everything in 
/opt/
 
> Thanks,
> Chris Packham.

Regards,
Andrew

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2016-02-10 21:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 20:32 Chris Packham
2016-02-10 20:41 ` Bryan Hundven
2016-02-10 20:49   ` Chris Packham
2016-02-10 20:52     ` Bryan Hundven
2016-02-10 21:05       ` Chris Packham
2016-02-10 21:43 ` andrew [this message]
2016-02-23  3:55   ` Chris Packham
2016-02-23  4:37     ` Bryan Hundven
2016-02-23  4:40     ` Bryan Hundven
2016-02-23 21:15       ` Chris Packham
2016-02-23 13:05     ` Thomas Petazzoni
2016-02-23 15:41       ` Bryan Hundven
2016-02-23 21:26         ` Github tags (was Re: crosstool-NG Debian packaging) Chris Packham
2016-02-12  4:20 ` crosstool-NG Debian packaging Chris Packham
2016-02-12 19:49   ` Bryan Hundven
2016-02-14 19:42     ` Chris Packham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4313479a694e9b4b91d7842dc4e3c690@cloud.ncrmnt.org \
    --to=andrew@ncrmnt.org \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=John.Collis@alliedtelesis.co.nz \
    --cc=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).