* Obsoletion procedures?
@ 2006-06-11 14:52 Max Bowsher
2006-06-11 18:24 ` Christopher Faylor
0 siblings, 1 reply; 5+ messages in thread
From: Max Bowsher @ 2006-06-11 14:52 UTC (permalink / raw)
To: cygwin-apps
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
Three of my library packages are going to be becoming obsolete in the
medium-term future.
libapr0 and libaprutil0 and their development packages apr and apr-util
are already used only by [prev] software.
libneon24 is used solely by [curr] cadaver, and [prev] subversion.
I'm soliciting opinions on how long library packages should remain after
they no longer are required by any other software in the distro.
Max.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Obsoletion procedures?
2006-06-11 14:52 Obsoletion procedures? Max Bowsher
@ 2006-06-11 18:24 ` Christopher Faylor
2006-06-13 11:49 ` Max Bowsher
0 siblings, 1 reply; 5+ messages in thread
From: Christopher Faylor @ 2006-06-11 18:24 UTC (permalink / raw)
To: cygwin-apps
On Sun, Jun 11, 2006 at 03:52:26PM +0100, Max Bowsher wrote:
>Three of my library packages are going to be becoming obsolete in the
>medium-term future.
>
>libapr0 and libaprutil0 and their development packages apr and apr-util
>are already used only by [prev] software.
>
>libneon24 is used solely by [curr] cadaver, and [prev] subversion.
>
>I'm soliciting opinions on how long library packages should remain after
>they no longer are required by any other software in the distro.
I don't think any opinions are required. We have a procedure for this.
The package move into the _obsolete category/_obsolete directory, and the
latest package becomes an empty .tar.bz2 file.
I don't see any reason to remove packages from the _obsolete category
once they are put there.
cgf
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Obsoletion procedures?
2006-06-11 18:24 ` Christopher Faylor
@ 2006-06-13 11:49 ` Max Bowsher
2006-06-13 17:26 ` Yaakov S (Cygwin Ports)
0 siblings, 1 reply; 5+ messages in thread
From: Max Bowsher @ 2006-06-13 11:49 UTC (permalink / raw)
To: cygwin-apps
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Christopher Faylor wrote:
> On Sun, Jun 11, 2006 at 03:52:26PM +0100, Max Bowsher wrote:
>> Three of my library packages are going to be becoming obsolete in the
>> medium-term future.
>>
>> libapr0 and libaprutil0 and their development packages apr and apr-util
>> are already used only by [prev] software.
>>
>> libneon24 is used solely by [curr] cadaver, and [prev] subversion.
>>
>> I'm soliciting opinions on how long library packages should remain after
>> they no longer are required by any other software in the distro.
>
> I don't think any opinions are required. We have a procedure for this.
> The package move into the _obsolete category/_obsolete directory, and the
> latest package becomes an empty .tar.bz2 file.
>
> I don't see any reason to remove packages from the _obsolete category
> once they are put there.
Sorry, I could have been clearer. The issue is that these are all
library packages, which people could conceivably have self-compiled
stuff depending upon.
I'd like some opinions on how long a real (not empty .tar) version of a
library should persist, after nothing in the distribution requires it
any more.
Max.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Obsoletion procedures?
2006-06-13 11:49 ` Max Bowsher
@ 2006-06-13 17:26 ` Yaakov S (Cygwin Ports)
2006-06-14 2:30 ` Charles Wilson
0 siblings, 1 reply; 5+ messages in thread
From: Yaakov S (Cygwin Ports) @ 2006-06-13 17:26 UTC (permalink / raw)
To: cygwin-apps
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Max Bowsher wrote:
> Sorry, I could have been clearer. The issue is that these are all
> library packages, which people could conceivably have self-compiled
> stuff depending upon.
>
> I'd like some opinions on how long a real (not empty .tar) version of a
> library should persist, after nothing in the distribution requires it
> any more.
The precedent seems to be to keep them indefinitely, unless they are
affected by security issues or are otherwise hopelessly broken.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEjvUgpiWmPGlmQSMRAicLAJ4+fMc4Hh2o7S451Zto899WNHbppQCdG/tP
XMBlkleQxvezJ91wDzPqkdE=
=YcO0
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Obsoletion procedures?
2006-06-13 17:26 ` Yaakov S (Cygwin Ports)
@ 2006-06-14 2:30 ` Charles Wilson
0 siblings, 0 replies; 5+ messages in thread
From: Charles Wilson @ 2006-06-14 2:30 UTC (permalink / raw)
To: CygWin-Apps
Yaakov S (Cygwin Ports) wrote:
> The precedent seems to be to keep them indefinitely, unless they are
> affected by security issues or are otherwise hopelessly broken.
Yep. Just dump 'em over in _obsolete, make a copy of
<PKG>-x.y.z-r-src.tar.bz2 named lib<PKG>N-x.y.z-r-src.tar.bz2, remove
the external-src: line in the lib's setup.hint, and let it rot.
--
Chuck
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-06-14 2:30 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-06-11 14:52 Obsoletion procedures? Max Bowsher
2006-06-11 18:24 ` Christopher Faylor
2006-06-13 11:49 ` Max Bowsher
2006-06-13 17:26 ` Yaakov S (Cygwin Ports)
2006-06-14 2:30 ` Charles Wilson
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).