Your message dated Sun, 23 Aug 2020 13:45:15 +0200
with message-id <5689332.mCtNnpuFJ4@thyrus>
and subject line Re: Should support adding a KDE component to an existing
source tree
has caused the Debian Bug report #261269,
regarding Should support adding a KDE component to an existing source tree
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 ow...@bugs.debian.org
immediately.)
--
261269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kapptemplate
Version: 4:3.2.3-2
Severity: wishlist
kapptemplate's only mode of operation seems to be
"create a new KDE project". It doesn't seem to be possible (and in fact
some of the configure functions it defines make it /im/possible) to add
a KDE component to an existing, autoconfiscated project, preferably as
an optional feature (that can be disabled in configure).
Daniel
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (ignored: LC_ALL set to en_US)
-- no debconf information
--- End Message ---
--- Begin Message ---
In data sabato 24 luglio 2004 21:43:30 CEST, Daniel Burrows ha scritto:
> Package: kapptemplate
> Version: 4:3.2.3-2
> Severity: wishlist
>
> kapptemplate's only mode of operation seems to be
> "create a new KDE project". It doesn't seem to be possible (and in fact
> some of the configure functions it defines make it /im/possible) to add
> a KDE component to an existing, autoconfiscated project, preferably as
> an optional feature (that can be disabled in configure).
The upstream bug report [1] was closed long ago with the following
explanation:
| out of KAppTemplate scope.
| In KDE 4.1, KAppTemplate projects are compatible with KDevelop so
| you'll be able to easily generate the same template from within
| KDevelop.
|
| KAppTemplate is only a template generator, nothing more. Once the
| project is generated, you read the included README and then you're
| on your own!
Since the scope of kapptemplate has not changed in all these years,
I'm closing this bug report.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
