public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
* libargp inconsistent packaging
@ 2016-09-09 12:11 Marco Atzeri
  2016-09-15 17:06 ` Andrew Schulman
  0 siblings, 1 reply; 6+ messages in thread
From: Marco Atzeri @ 2016-09-09 12:11 UTC (permalink / raw)
  To: cygwin-apps

Andrew,

should be better to create a separate package
libargp-devel for the development portion ?


$ cygcheck -l libargp
/usr/bin/cygargp-0.dll
/usr/include/argp.h
/usr/lib/libargp.dll.a
/usr/share/doc/Cygwin/libargp.README
/usr/share/doc/libargp/COPYING
/usr/share/doc/libargp/COPYING.LESSER
/usr/share/doc/libargp/README.Cygwin


the libargp should contain only:
/usr/bin/cygargp-0.dll

Regards
MArco

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libargp inconsistent packaging
  2016-09-09 12:11 libargp inconsistent packaging Marco Atzeri
@ 2016-09-15 17:06 ` Andrew Schulman
  2016-09-15 18:29   ` Achim Gratz
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Schulman @ 2016-09-15 17:06 UTC (permalink / raw)
  To: cygwin-apps

> Andrew,
> 
> should be better to create a separate package
> libargp-devel for the development portion ?
> 
> 
> $ cygcheck -l libargp
> /usr/bin/cygargp-0.dll
> /usr/include/argp.h
> /usr/lib/libargp.dll.a
> /usr/share/doc/Cygwin/libargp.README
> /usr/share/doc/libargp/COPYING
> /usr/share/doc/libargp/COPYING.LESSER
> /usr/share/doc/libargp/README.Cygwin
> 
> 
> the libargp should contain only:
> /usr/bin/cygargp-0.dll
> 
> Regards
> MArco

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.

However if I'm wrong and it's really better to split the package, I can
certainly do that.

Andrew

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libargp inconsistent packaging
  2016-09-15 17:06 ` Andrew Schulman
@ 2016-09-15 18:29   ` Achim Gratz
  2016-09-16  9:16     ` Andrew Schulman
  0 siblings, 1 reply; 6+ messages in thread
From: Achim Gratz @ 2016-09-15 18:29 UTC (permalink / raw)
  To: cygwin-apps

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libargp inconsistent packaging
  2016-09-15 18:29   ` Achim Gratz
@ 2016-09-16  9:16     ` Andrew Schulman
  2016-09-16 10:20       ` Marco Atzeri
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Schulman @ 2016-09-16  9:16 UTC (permalink / raw)
  To: cygwin-apps

> 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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libargp inconsistent packaging
  2016-09-16  9:16     ` Andrew Schulman
@ 2016-09-16 10:20       ` Marco Atzeri
  2016-09-18 23:40         ` Andrew Schulman
  0 siblings, 1 reply; 6+ messages in thread
From: Marco Atzeri @ 2016-09-16 10:20 UTC (permalink / raw)
  To: cygwin-apps

On 16/09/2016 11:15, Andrew Schulman wrote:
>> 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.


we need just 2 packages
that is more or less the default split

libargp
/usr/bin/cygargp-0.dll

libargp-devel
/usr/include/argp.h
/usr/lib/libargp.dll.a
/usr/share/doc/Cygwin/libargp.README
/usr/share/doc/libargp/COPYING
/usr/share/doc/libargp/COPYING.LESSER
/usr/share/doc/libargp/README.Cygwin

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: libargp inconsistent packaging
  2016-09-16 10:20       ` Marco Atzeri
@ 2016-09-18 23:40         ` Andrew Schulman
  0 siblings, 0 replies; 6+ messages in thread
From: Andrew Schulman @ 2016-09-18 23:40 UTC (permalink / raw)
  To: cygwin-apps

> On 16/09/2016 11:15, Andrew Schulman wrote:
> >> 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.
> 
> 
> we need just 2 packages
> that is more or less the default split
> 
> libargp
> /usr/bin/cygargp-0.dll
> 
> libargp-devel
> /usr/include/argp.h
> /usr/lib/libargp.dll.a
> /usr/share/doc/Cygwin/libargp.README
> /usr/share/doc/libargp/COPYING
> /usr/share/doc/libargp/COPYING.LESSER
> /usr/share/doc/libargp/README.Cygwin

OK then

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-09-18 23:40 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-09 12:11 libargp inconsistent packaging Marco Atzeri
2016-09-15 17:06 ` Andrew Schulman
2016-09-15 18:29   ` Achim Gratz
2016-09-16  9:16     ` Andrew Schulman
2016-09-16 10:20       ` Marco Atzeri
2016-09-18 23:40         ` Andrew Schulman

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).