Popt package split planning

[Panu Matilainen]

On Wed, 22 Aug 2007, Robert Scheck wrote:

> Good evening all,
>
> On Tue, 14 Aug 2007, Panu Matilainen wrote:
>> Thought I'd post this to -maintainers for potential discussion first before
>> going to -devel-announce...
>
> thank you to Panu at first. When is a good point to spam via -maintainers?
> Once the package got built? Before? Now?

I'd say right now. And also drop a note to fedora-devel-announce.

>> To ease transition, starting from the next rawhide push, the popt package
>> that's still built from rpm.spec adds
>> Provides: popt-devel = %{version}-%{release}
>> so you can start adding the buildrequires for the packages needing it
>
> Hopefully everybody added the correct dependency. If not, do so otherwise
> your package will break at the next rebuild...

A quick grep of full up-to-date cvs tree shows that nobody did. Oh well...

>> already. Once the new popt package is reviewed and published to
>> repositories, rpm will be changed to build against that and drop the
>> internal popt entirely.
>
> It's likely, that tomorrow will be the day, where popt will get rebuilt for
> the development branch (once CVS is done). After that, RPM needs to get the
> internal popt removed.

Yup, mostly done and will be committing the changes to cvs in a moment to 
be ready for just make tag + build once the new popt goes in.

 	- Panu -