From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: libargp inconsistent packaging
Date: Thu, 15 Sep 2016 18:29:00 -0000 [thread overview]
Message-ID: <877fad6mpr.fsf@Rainer.invalid> (raw)
In-Reply-To: <aokltb5k76v3v5v442514u97k07p3tpmmn@4ax.com> (Andrew Schulman's message of "Thu, 15 Sep 2016 13:06:10 -0400")
Andrew Schulman writes:
> Hi Marco. I think I thought about this in the past, but because the total
> size of this package is so small, I decided it wasn't worth the trouble to
> split it in two. I think that both packages would have to include the doc
> files, so there wouldn't be much gain.
You can't have the same files in two different packages, so if you
wanted to do that you'd need to psplit out a doc package as well and
have that as a required package for the other two.
> However if I'm wrong and it's really better to split the package, I can
> certainly do that.
I'm not saying this is urgent, but maybe the next time you need to
package libargp anyway you might do what I've outlined above. Provided
you use cygport it isn't any burden past the initial setup and it's
cleaner for other packages that depend on this one.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2016-09-15 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 12:11 Marco Atzeri
2016-09-15 17:06 ` Andrew Schulman
2016-09-15 18:29 ` Achim Gratz [this message]
2016-09-16 9:16 ` Andrew Schulman
2016-09-16 10:20 ` Marco Atzeri
2016-09-18 23:40 ` Andrew Schulman
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=877fad6mpr.fsf@Rainer.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).