On Thu, Sep 30, 2021 at 10:24:01AM +0200, Alec Leamas wrote:
> Just for the record: the issue about packaging wxWidgets 3.1 has already
> been discussed with the maintainer:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919903
Hi Alec, I get the impression there that the maintainer is
On 26/09/2021 19:03, Alec Leamas wrote:
Hi Jonas,
On 26/09/2021 14:41, Jonas Smedegaard wrote:
I deliberately ignored the timing part of your proposal, and instead
think in "stages" - here is a plan I find sensible:
* maybe you make an test packaging of 3.1.5 - not uploaded to Debian at
I'm raising this issue in time...
I also share your view that if bundling, it must be a temporary
measure. It must definitely not linger in upcoming releases.
Sounds like we agree, then - sorry if I mistook you as less careful in
my previous remarks...
No offense taken ;)
Is there a rout
ou call "provisionary" is something done outside of Debian
> > or only in Debian experimental, then is seems you agree. But I am
> > not sure - in particular your "and uses that in next cycle" sounds
> > like you will not treat it as only experimental but re
On 2021-09-26 12:16 +0200, Alec Leamas wrote:
> > See https://wiki.debian.org/PkgKde/DhSymbolsFile
>
> After some tries in this area I have leaned to Russ Allberry's post
> https://www.eyrie.org/~eagle/journal/2012-02/001.html. Is this outdated?
That KDE tool does help a lot but for large C++
ided if possible. After all, I'm raising this issue in time...
I also share your view that if bundling, it must be a temporary measure.
It must definitely not linger in upcoming releases.
Is there a route where we keep things in experimental (bundled or not)
and let it stay there until wxWid
Quoting Alec Leamas (2021-09-26 10:05:04)
> Hi Jonas,
>
>
> Thanks for taking time to try to sort this out!
>
> On 25/09/2021 18:52, Jonas Smedegaard wrote:
> > Quoting Alec Leamas (2021-09-25 18:23:42)
> >> On 25/09/2021 18:04, Jonas Smedegaard wrote:
> >>> Quoting Alec Leamas (2021-09-25
Hi Jonas,
Thanks for taking time to try to sort this out!
On 25/09/2021 18:52, Jonas Smedegaard wrote:
Quoting Alec Leamas (2021-09-25 18:23:42)
On 25/09/2021 18:04, Jonas Smedegaard wrote:
Quoting Alec Leamas (2021-09-25 17:47:04)
So, the question: would it be acceptable to bundle the
Quoting Alec Leamas (2021-09-25 18:23:42)
> On 25/09/2021 18:04, Jonas Smedegaard wrote:
> > Quoting Alec Leamas (2021-09-25 17:47:04)
> >>
> >> So, the question: would it be acceptable to bundle the wxWidgets
> >> 3.1.5 sources in next OpenCPN release in such a situation?
> >>
> >
> > How do
Hi Jonas,
On 25/09/2021 18:04, Jonas Smedegaard wrote:
Hi Alec,
Quoting Alec Leamas (2021-09-25 17:47:04)
So, the question: would it be acceptable to bundle the wxWidgets 3.1.5
sources in next OpenCPN release in such a situation?
How do you and OpenCPN upstream expect to handle bugs for
Hi Alec,
Quoting Alec Leamas (2021-09-25 17:47:04)
> Trying to plan the future for the OpenCPN package. Upstream is
> currently shipping a beta, and eventually it will be released and
> packaged.
>
> In next cycle upstream might update the wxWidgets dependency from 3.0
> to 3.1.5. This is
Dear list,
Trying to plan the future for the OpenCPN package. Upstream is currently
shipping a beta, and eventually it will be released and packaged.
In next cycle upstream might update the wxWidgets dependency from 3.0 to
3.1.5. This is problematic, since wxWidgets offers no ABI stability
Adam Borowski writes:
> If, for whatever reason, you feel urgency, the ftpmasters are very good at
> prioritizing your needs. There's just no information attached to packages
> normally -- you need to let them know. One way is popping up in #debian-ftp
> and whining.
>
> I've never had them
On Wed, May 20, 2020 at 09:54:56PM +0100, Wookey wrote:
> I think that is ultimately up to you as the maintainer. If it's really
> important to get the new version uploaded, then yeah do that first,
> but otherwise just leave it at the current version, do the new
> library, then upload new version
On 2020-05-20 17:51 +0200, Gard Spreemann wrote:
>
> Ah, but one of the packages is in Debian and has been for a while. It's
> just that the latest upstream version of *that package* has started
> bundling a third-party library that wasn't used in any way before.
>
> Now th
Wookey writes:
> On 2020-05-20 13:42 +0200, Gard Spreemann wrote:
>>
>> Wookey writes:
>
>> Is there any community consensus on putting the bundling in place
>> temporarily while the separate package is held up in NEW? Being the
>> maintainer of bo
On 2020-05-20 13:42 +0200, Gard Spreemann wrote:
>
> Wookey writes:
> Is there any community consensus on putting the bundling in place
> temporarily while the separate package is held up in NEW? Being the
> maintainer of both, I would be able to quickly react to the separate
&
Wookey writes:
> On 2020-05-20 10:16 +0200, Gard Spreemann wrote:
>> Hi list,
>>
>> Upstream for a package I maintain has as of its latest release started
>> bundling and requiring a third-party header-only library. I am
>> considering packaging that third
On 2020-05-20 10:16 +0200, Gard Spreemann wrote:
> Hi list,
>
> Upstream for a package I maintain has as of its latest release started
> bundling and requiring a third-party header-only library. I am
> considering packaging that third-party library (it's useful to me, at
> the
Hi list,
Upstream for a package I maintain has as of its latest release started
bundling and requiring a third-party header-only library. I am
considering packaging that third-party library (it's useful to me, at
the very least) but I think it's a borderline case of whether it
warrants being
//github.com/rollup/rollup-plugin-replace#readme
* License : Expat
Programming Lang: JavaScript
Description : Rollup plugin to make string substitutions while
bundling
This rollup plugin replaces strings in files during the bundling stage
; you
should ensure it is run early in
Programming Lang: JavaScript
Description : convenience package bundling LevelUP LevelDOWN -
Node.js module
This is a convenience package that bundles the current release of LevelUP
and
LevelDOWN and exposes LevelUP on its export.
.
Use this package to avoid having to explicitly install
22 matches
Mail list logo
