Bug#88486: marked as done (libapt-pkg: Threadsafe accessor methods for OpProgress, pkgAcquireStatus)
Your message dated Fri, 14 Aug 2015 15:03:09 +0200
with message-id <20150814150138.GA24258@debian.org>
and subject line Re: Bug#88486: libapt-pkg: Accessor methods for OpProgress, threadsafety
has caused the Debian Bug report #88486,
regarding libapt-pkg: Threadsafe accessor methods for OpProgress, pkgAcquireStatus
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
88486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88486
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.5.0
Severity: wishlist
Hi,
I'm currently building a multithreaded application on top of libapt-pkg,
which is supposed to run a few operations in the background. For this, I'm
using a subclass of OpProgress which does not make any output or assume
validity of the standard streams and can be queried about the current values.
In some cases, I'd like to use OpTextProgress as a replacement for this class,
however if I give an OpProgress object to my class, I can no longer access my
accessor methods (of course :-) ). Would it be possible to have accessor
methods in OpProgress, possibly even with pthreads style locking around methods
which get/set multiple values (to avoid display oddities)?
I haven't provided a patch since I know you have a different method naming
convention (I use the Java style), so I didn't know how to name the methods.
Simon
-- System Information
Debian Release: 2.2
Architecture: m68k
Kernel: Linux lasagna.hogyros 2.0.36 #2 Sat Feb 6 22:57:25 CET 1999 m68k
Versions of packages apt depends on:
ii libc6 2.1.3-13 GNU C Library: Shared libraries an
ii libstdc++2.10-glibc2.1 1:2.95.2-13.1 The GNU stdc++ library
--- End Message ---
--- Begin Message ---
On Sun, Mar 04, 2001 at 05:59:37PM +0100, Simon Richter wrote:
> Package: apt
> Version: 0.5.0
> Severity: wishlist
>
> Hi,
>
> I'm currently building a multithreaded application on top of libapt-pkg,
> which is supposed to run a few operations in the background. For this, I'm
> using a subclass of OpProgress which does not make any output or assume
> validity of the standard streams and can be queried about the current values.
>
> In some cases, I'd like to use OpTextProgress as a replacement for this class,
> however if I give an OpProgress object to my class, I can no longer access my
> accessor methods (of course :-) ). Would it be possible to have accessor
> methods in OpProgress, possibly even with pthreads style locking around methods
> which get/set multiple values (to avoid display oddities)?
>
> I haven't provided a patch since I know you have a different method naming
> convention (I use the Java style), so I didn't know how to name the methods.
>
> Simon
>
We won't make any part of APT thread-safe. You could now do those things
by sending status updates via D-Bus or something like that anyway.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
--- End Message ---
Reply to: