public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: "build-essential" metapackage [WAS: FW: gecko Segmentation fault when compiling]
Date: Thu, 30 Aug 2018 08:50:00 -0000	[thread overview]
Message-ID: <05b11c41-c760-03a8-e6eb-5d8685349015@gmail.com> (raw)
In-Reply-To: <774189134.20180829130119@yandex.ru>

On 8/29/2018 6:01 AM, Andrey Repin wrote:
> 
> I think we need a "build-essential" metapackage.
> 

I would suggest base-devel as the name of the metapackage.  But what
exactly should that include?  Should there be more than one metapackage
that adds more complex tools?

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2018-08-29 20:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 12:44 FW: gecko Segmentation fault when compiling tlake
2018-08-26 13:56 ` Marco Atzeri
     [not found]   ` <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADPibjNochZQoAsZaGDyawCAQAAAAA=@twcny.rr.com>
2018-08-27  9:09     ` Marco Atzeri
2018-08-27 19:20       ` cyg Simple
2018-08-29 10:05         ` tlake
2018-08-29 11:16           ` Andrey Repin
2018-08-29 13:05             ` tlake
2018-08-30  6:40               ` Andrey Repin
2018-08-30  7:13                 ` tlake
2018-08-30  8:50             ` cyg Simple [this message]
2018-08-30  9:30               ` "build-essential" metapackage [WAS: FW: gecko Segmentation fault when compiling] Andrey Repin
2018-08-30  0:35           ` FW: gecko Segmentation fault when compiling Marco Atzeri

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=05b11c41-c760-03a8-e6eb-5d8685349015@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).