public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: perl_base not in Base ?
Date: Wed, 29 Dec 2021 16:12:17 +0000	[thread overview]
Message-ID: <e1f15ff8-0873-8f6c-ed33-953ba2b66640@dronecode.org.uk> (raw)
In-Reply-To: <6f6dc496-455e-792a-b7d0-a65011bbaadf@cornell.edu>

On 29/12/2021 14:25, Ken Brown wrote:
> On 12/29/2021 3:51 AM, Achim Gratz wrote:
>> Am 28.12.2021 um 11:57 schrieb Marco Atzeri:
>>> I had the impression it was in the Base category
>>>
>>> @ perl_base
>>> sdesc: "Perl programming language interpreter"
>>> ldesc: "Perl programming language interpreter
>>
>> That split was indeed made to enable making it available for Base 
>> packages, but that decision was never made I think.
> 
> It makes sense to me to add it to Base.  Were there any objections when 
> that was proposed before?
> 
>>> Or is it supposed to be pulled by another Base program ?

I think this was the case, at one time.

I believe something (chkdupexe?) in the 'util-linux' package (which is 
in base) used to be written in perl, and so brought in perl_base.

I think it's since been rewritten in C. So nothing in the base category 
requires perl_base currently (and hopefully in the future :)).

>> Base packages should not pull in non-Base packages, but it appears 
>> that info currently fails that requirement.
> 
> A lot of packages fail that requirement.  I don't think it should be a 
> requirement.  To me, Base packages are those that we've decided should 
> be in every Cygwin installation.  If that forces other packages to be 
> installed, so be it.

Yeah.  It shouldn't be the case that libX is in base just because it's 
required by P, so we have to notice, remember and check if it can be 
removed when P changes to require libY instead...

  parent reply	other threads:[~2021-12-29 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 10:57 Marco Atzeri
2021-12-29  8:51 ` Achim Gratz
2021-12-29 14:25   ` Ken Brown
2021-12-29 14:36     ` Marco Atzeri
2021-12-29 16:12     ` Jon Turney [this message]
2021-12-30 10:38       ` Achim Gratz
2021-12-30 13:34         ` Ken Brown
2021-12-30 10:36     ` Achim Gratz

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=e1f15ff8-0873-8f6c-ed33-953ba2b66640@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@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).