From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: libargp inconsistent packaging
Date: Fri, 16 Sep 2016 09:16:00 -0000 [thread overview]
Message-ID: <3vdntbh1h667ceajf0vc4g4f59am4f1ab7@4ax.com> (raw)
In-Reply-To: <877fad6mpr.fsf@Rainer.invalid>
> 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.
That would REALLY be overkill. No, they wouldn't be the same files, since they'd
be in /usr/share/doc/libargp and /usr/share/doc/libargp-devel.
next prev parent reply other threads:[~2016-09-16 9:16 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
2016-09-16 9:16 ` Andrew Schulman [this message]
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=3vdntbh1h667ceajf0vc4g4f59am4f1ab7@4ax.com \
--to=schulman.andrew@epa.gov \
--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).