public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] fortune-mod - please review
Date: Mon, 12 Apr 2021 07:52:21 +0200	[thread overview]
Message-ID: <874kgcvylm.fsf@Otto.invalid> (raw)
In-Reply-To: <859fa65b-5aab-7926-532b-b266cc15daaf@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 11 Apr 2021 18:00:22 -0600")

Brian Inglis writes:
> On 2021-04-11 13:44, Achim Gratz wrote:
>> Brian Inglis writes:
>>> I just ran cpan Path:Tiny which also updated Unicode::UTF8,
>>> Test::MockRandom, and Test::FailWarnings.
>> Leave your hands off CPAN when you do packaging.
>
> I would like to, but do not know how else to easily install unpackaged
> prereqs for a build.

You don't.  You package them or request them to get packaged, then use
the installed package.

> What's required to package App::XML::DocBook::Builder, is there a good
> package to use as a template, and are there any special considerations
> for perl packages?

In this particular case seemingly that does nothing but build a
Makefile, so I'd rather try to figure out a way to live without it.  And
yes, there are special considerations for Perl packages, given that some
patches for getting the correct dependencies in have not yet made it
into the official cygport.

>>> It looks like something about perl-Path-Tiny and/or prereqs was messed
>>> up here, but is no longer.
>> No, you not comprehending what you're doing there is more likely.
>
> I did not comprehend why setup_x86 complained about installing
> perl-Path-Tiny, so I told it to go ahead, as deinstalling perl_vendor
> seemed drastic, with a lot of dependencies, and I could only see it in
> mirror/x86/setup.ini:

That particular package has been obsolete since at least 2015 and its
ghost existence on your system is just another indication that this
installation hasn't been properly maintained and is unsuitable for
packaging work (and unlikely to work correctly otherwise).  I don't
really care what you do with your own installation, but please keep
separate x86 and x86_64 installations that you use just for packaging
and are current with the latest updates with no orphaned packages
installed when you start each build.

I think I'll re-add obsoletes: hints to all existing Perl versions.

> There seem to be some discrepancies between arches in setup.ini:

Again, I'm fairly certain that most of these are long obsolete and just
kept because some not-yet removed older package version still refers to
them.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2021-04-12  5:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 16:49 Brian Inglis
2021-04-11 15:16 ` Jon Turney
2021-04-11 18:47   ` Brian Inglis
2021-04-11 19:44     ` Achim Gratz
2021-04-12  0:00       ` Brian Inglis
2021-04-12  5:52         ` ASSI [this message]
2021-06-01  5:36           ` [ITP] perl-App-XML-DocBook-Builder [ITA] fortune-mod Brian Inglis
2021-06-01 17:39             ` Marco Atzeri
2021-06-05 15:40               ` Achim Gratz
2021-06-05 16:19                 ` Marco Atzeri
2021-06-05 21:43                 ` Brian Inglis

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=874kgcvylm.fsf@Otto.invalid \
    --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).