From: Achim Gratz <Stromeko@Nexgo.DE>
To: cygwin-apps@cygwin.com
Subject: Re: perl_base not in Base ?
Date: Thu, 30 Dec 2021 11:36:12 +0100 [thread overview]
Message-ID: <51253d15-02aa-65b8-a82d-973d9781dbf2@Nexgo.DE> (raw)
In-Reply-To: <6f6dc496-455e-792a-b7d0-a65011bbaadf@cornell.edu>
Am 29.12.2021 um 15:25 schrieb Ken Brown:
> It makes sense to me to add it to Base. Were there any objections when
> that was proposed before?
I don't remember, honestly. There were/are a few problems w/ cygport
trying to pull in perl as a dependency for perl_base, but I've patched
those out locally. Again, most if not all Linux distributions have
perl_base in their default installation so it can be used in system
scripts. We don't have these at the moment, but we might want to later on.
>>> Or is it supposed to be pulled by another Base program ?
>>
>> 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.
As long as there is no distinction between required and recommended in
our packaging system I think we should not have packages that are
required from Base packages, but are not themselves in Base, e.g.
installing "Category Base" should be idempotent with installing all
packages in category Base.
We have a bunch of packages that are deliberately split so that one of
them can be in category base without pulling in hundreds of dependencies
that are only needed for optional functionality.
--
Achim.
(on the road :-)
prev parent reply other threads:[~2021-12-30 10:36 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
2021-12-30 10:38 ` Achim Gratz
2021-12-30 13:34 ` Ken Brown
2021-12-30 10:36 ` Achim Gratz [this message]
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=51253d15-02aa-65b8-a82d-973d9781dbf2@Nexgo.DE \
--to=stromeko@nexgo.de \
--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).