Re: [ITA] libapr1-1.3.3-1

2008-10-07 Thread Corinna Vinschen
On Oct  6 08:13, David Rothenberger wrote:
 On 10/6/2008 1:09 AM, Corinna Vinschen wrote:
 On Sep 29 18:34, Corinna Vinschen wrote:
 On Sep 15 08:25, David Rothenberger wrote:
 Ping.

 Is there anything else I need to do for this package before it is 
 uploaded?
 If nobody else is looking into these packages, I'll do it later this
 week.
 I didn't forget and I still have this on my plate.  I'm still not quite
 back to normal, sorry.

 No problem. I understand that it can take a while to get back to normal 
 after a holiday.

Holiday + Sickness = :(   Only the holiday is over, though.

I had a quick look and the basic packaging looks ok.  What bugs me
a bit is the new layout.

Old:

  apr1 --- libapr1

New:

  libapr1 -+- apr1
   +- libapr1-devel

I guess we should better move the apr1 dir into the _obsolete dir, then
just leave the libapr1 dir at top level:

  _obsolete --- apr1
  libapr1   --- libapr1-devel

Same for the aprutil1/libaprutil1 dirs.  Is that what you intended?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat


Re: [ITA] libapr1-1.3.3-1

2008-10-07 Thread David Rothenberger

On 10/7/2008 7:43 AM, Corinna Vinschen wrote:

On Oct  6 08:13, David Rothenberger wrote:

On 10/6/2008 1:09 AM, Corinna Vinschen wrote:

On Sep 29 18:34, Corinna Vinschen wrote:

On Sep 15 08:25, David Rothenberger wrote:

Ping.

Is there anything else I need to do for this package before it is 
uploaded?

If nobody else is looking into these packages, I'll do it later this
week.

I didn't forget and I still have this on my plate.  I'm still not quite
back to normal, sorry.
No problem. I understand that it can take a while to get back to normal 
after a holiday.


Holiday + Sickness = :(   Only the holiday is over, though.


Sorry to hear that. I hope you feel better soon.


I had a quick look and the basic packaging looks ok.  What bugs me
a bit is the new layout.

Old:

  apr1 --- libapr1

New:

  libapr1 -+- apr1
   +- libapr1-devel

I guess we should better move the apr1 dir into the _obsolete dir, then
just leave the libapr1 dir at top level:

  _obsolete --- apr1
  libapr1   --- libapr1-devel

Same for the aprutil1/libaprutil1 dirs.  Is that what you intended?


I hadn't thought about the directory layout, but I think that will work. 
apr1 and aprutil1 are both empty transition packages that are marked 
obsolete, so they can (should?) go under _obsolete I guess.


Do you want me to restructure the packages on my server to match this 
layout?


--
David Rothenberger    [EMAIL PROTECTED]

Steinbach's Guideline for Systems Programming:
Never test for an error condition you don't know how to handle.



Re: [ITA] libapr1-1.3.3-1

2008-10-07 Thread Corinna Vinschen
On Oct  7 08:12, David Rothenberger wrote:
 On 10/7/2008 7:43 AM, Corinna Vinschen wrote:
 I guess we should better move the apr1 dir into the _obsolete dir, then
 just leave the libapr1 dir at top level:
   _obsolete --- apr1
   libapr1   --- libapr1-devel
 Same for the aprutil1/libaprutil1 dirs.  Is that what you intended?

 I hadn't thought about the directory layout, but I think that will work. 
 apr1 and aprutil1 are both empty transition packages that are marked 
 obsolete, so they can (should?) go under _obsolete I guess.

 Do you want me to restructure the packages on my server to match this 
 layout?

No worries, I did that on sourceware.  Uploaded.  Thanks for taking
over maintainership!


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat


Re: [ITA] libapr1-1.3.3-1

2008-10-06 Thread Corinna Vinschen
On Sep 29 18:34, Corinna Vinschen wrote:
 On Sep 15 08:25, David Rothenberger wrote:
  Ping.
 
  Is there anything else I need to do for this package before it is uploaded?
 
 If nobody else is looking into these packages, I'll do it later this
 week.

I didn't forget and I still have this on my plate.  I'm still not quite
back to normal, sorry.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat


Re: [ITA] libapr1-1.3.3-1

2008-10-06 Thread David Rothenberger

On 10/6/2008 1:09 AM, Corinna Vinschen wrote:

On Sep 29 18:34, Corinna Vinschen wrote:

On Sep 15 08:25, David Rothenberger wrote:

Ping.

Is there anything else I need to do for this package before it is uploaded?

If nobody else is looking into these packages, I'll do it later this
week.


I didn't forget and I still have this on my plate.  I'm still not quite
back to normal, sorry.


No problem. I understand that it can take a while to get back to normal 
after a holiday.


--
David Rothenberger    [EMAIL PROTECTED]

Bombeck's Rule of Medicine:
Never go to a doctor whose office plants have died.



Re: [ITA] libapr1-1.3.3-1

2008-09-29 Thread Corinna Vinschen
On Sep 15 08:25, David Rothenberger wrote:
 Ping.

 Is there anything else I need to do for this package before it is uploaded?

If nobody else is looking into these packages, I'll do it later this
week.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat


Re: [ITA] libapr1-1.3.3-1

2008-09-15 Thread David Rothenberger

Ping.

Is there anything else I need to do for this package before it is uploaded?

On 9/1/2008 1:01 AM, David Rothenberger wrote:

On 8/31/2008 11:14 PM, David Rothenberger wrote:

On 8/31/2008 8:05 PM, Brian Dessent wrote:

David Rothenberger wrote:


I've changed the package structure as follows:
~ * libapr1: Runtime library and documentation.
~ * libapr1-devel: Development headers and libraries.
~ * apr1: Source package.

Something seems wrong here.

[snip]

Okay, so you want to rename apr1 to apr1-devel, that makes some sense.
But why does apr1 continue to contain just the source?  Why not just
have apr1-devel contain the source and make apr1 a completely empty
package?

Okay. I'll rebuild with apr1 being an empty transition package and
libapr1 containing the source.


Okay, here are the updated packages.

I've changed the package structure as follows:
 * libapr1: Runtime library and documentation.
 * libapr1-devel: Development headers and libraries.
 * apr1: Empty transition library.

apr1 is marked obsolete and depends on libapr1-devel to provide a
transition from the old package structure.

apr1 setup.hint
--
category: _obsolete
requires: libapr1-devel
external-source: libapr1
sdesc: Apache Portable Runtime core library (transition package)
ldesc: The mission of the Apache Portable Runtime (APR) project is to
create and maintain software libraries that provide a predictable and
consistent interface to underlying platform-specific implementations.
The primary goal is to provide an API to which software developers may
code and be assured of predictable if not identical behaviour regardless
of the platform on which their software is built, relieving them of the
need to code special-case conditions to work around or take advantage of
platform-specific deficiencies or features.

libapr1 setup.hint
--
category: Libs
requires: cygwin
sdesc: Apache Portable Runtime core library (runtime)
ldesc: The mission of the Apache Portable Runtime (APR) project is to
create and maintain software libraries that provide a predictable and
consistent interface to underlying platform-specific implementations.
The primary goal is to provide an API to which software developers may
code and be assured of predictable if not identical behaviour regardless
of the platform on which their software is built, relieving them of the
need to code special-case conditions to work around or take advantage of
platform-specific deficiencies or features.

libapr1-devel setup.hint
--
category: Libs
requires: cygwin libapr1
external-source: libapr1
sdesc: Apache Portable Runtime core library (Development)
ldesc: The mission of the Apache Portable Runtime (APR) project is to
create and maintain software libraries that provide a predictable and
consistent interface to underlying platform-specific implementations.
The primary goal is to provide an API to which software developers may
code and be assured of predictable if not identical behaviour regardless
of the platform on which their software is built, relieving them of the
need to code special-case conditions to work around or take advantage of
platform-specific deficiencies or features.

download:

wget -x -nH --cut-dirs=2 \
  http://mysite.verizon.net/res00a7j/cygwin/libapr1/apr1/apr1-1.3.3-1.tar.bz2 \
  http://mysite.verizon.net/res00a7j/cygwin/libapr1/apr1/setup.hint \
  http://mysite.verizon.net/res00a7j/cygwin/libapr1/libapr1-1.3.3-1-src.tar.bz2 
\
  http://mysite.verizon.net/res00a7j/cygwin/libapr1/libapr1-1.3.3-1.tar.bz2 \
  
http://mysite.verizon.net/res00a7j/cygwin/libapr1/libapr1-devel/libapr1-devel-1.3.3-1.tar.bz2
 \
  http://mysite.verizon.net/res00a7j/cygwin/libapr1/libapr1-devel/setup.hint \
  http://mysite.verizon.net/res00a7j/cygwin/libapr1/setup.hint





--
David Rothenberger    [EMAIL PROTECTED]

Sex is like air.  It's only a big deal if you can't get any.