[wpkg-users] Workaround for... Re: [Bug 131] pinpointing a package to a certain revision

[Dominik Hertel]

Well I could think of something like this for myself but it's cumbersome...
Also I have the impression that wpkg isn't very actively developed, is it?
I'm currently working on a GUI for package management and by doing so also
found some other things that could be implemented into the script... But I'm
really scared of changing anything in the script by myself, for it's really
huge... I couldn't even find a browseable api documentation even though it's
in the code!

so: is there still some active development going on?

2011/5/17 Dave Ewart <davee at ceu.ox.ac.uk>

> On Tuesday, 17.05.2011 at 09:08 +0200, bugzilla-daemon at bugzilla.wpkg.orgwrote:
>
> > http://bugzilla.wpkg.org/show_bug.cgi?id=131
> >
> > Dominik Hertel <dhertel at gmail.com> changed:
> >
> >            What    |Removed                     |Added
> >
> ----------------------------------------------------------------------------
> >            Priority|P2                          |P1
> >                  CC|                            |dhertel at gmail.com
> >             Version|0.9.10                      |1.1.2
> >          OS/Version|Windows 2000                |All
> >
> > --- Comment #2 from Dominik Hertel <dhertel at gmail.com>  ---
> > woa... just saw how old this ticket is... has this ever been implemented
> since?
> > it would really be great to see this feature
>
> I asked about a slightly different way of achieving a similar thing just
> last month: see
> http://lists.wpkg.org/pipermail/wpkg-users/2011-April/007340.html for
> the responses.
>
> I found a mixture of a few of them to be a useful approach.
>
> Dave.
>
> --
> Dave Ewart
> davee at ceu.ox.ac.uk
> Computing Manager, Cancer Epidemiology Unit
> University of Oxford / Cancer Research UK
> N 51.7516, W 1.2152
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20110517/80bb84d0/attachment-0002.html>