[csw-pkgsubmissions] newpkgs librsync

[Maciej (Matchek) Blizinski]

On Tue, Mar 16, 2010 at 4:02 PM, Sebastian Kayser <skayser at opencsw.org> wrote:
> * Philip Brown <phil at bolthole.com> wrote:
>> On Tue, Mar 16, 2010 at 12:54 AM, Brian Hill <bchill at opencsw.org> wrote:
>> > * librsync: new package
>> >  + librsync-0.9.7,REV=2010.03.16-SunOS5.8-i386-CSW.pkg.gz
>> >  + librsync-0.9.7,REV=2010.03.16-SunOS5.8-sparc-CSW.pkg.gz
>> >
>>
>> sigh. it's a mess in newpkgs.
>> Please clean up all older and non-desired versions of "librsync-*",
>> and then let me know.
>
> For users of submitpkg this is unfortunately an opaque detail. Maciej,
> could submitpkg be enhanced to prune old versions? Phil, as Brian is new
> to this game, what do you think about just considering the most current
> submitted version?
>
> skayser at bender:/home/newpkgs$ ls -1tr librsync-0.9.7\,REV\=2010.03.1*
> librsync-0.9.7,REV=2010.03.11-SunOS5.8-i386-CSW.pkg.gz
> librsync-0.9.7,REV=2010.03.11-SunOS5.8-sparc-CSW.pkg.gz
> librsync-0.9.7,REV=2010.03.16-SunOS5.8-i386-UNCOMMITTED.pkg.gz
> librsync-0.9.7,REV=2010.03.16-SunOS5.8-sparc-UNCOMMITTED.pkg.gz
> librsync-0.9.7,REV=2010.03.16-SunOS5.8-i386-CSW.pkg.gz
> librsync-0.9.7,REV=2010.03.16-SunOS5.8-sparc-CSW.pkg.gz

The definition of "most recent" needs some work.  There's an algorithm
that determines it, and it's not lexical sorting.  I can implement
something like this:

"if package foo is sent for release, anything matching foo-* that is
not what we're currently sending, gets deleted from
bender:/home/newpkgs"