On 06.07.18 22:00, Colin Watson wrote:
> If the libraries in question are DFSG-free themselves, there's no DFSG
> issue and you don't need to remove them from the tarball (and we'd
> generally encourage not modifying the upstream tarball unnecessarily for
> upload to Debian). The policy about
On Wed, 2018-07-11 at 08:57 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> But no, my real fear here was a tool more in the cpack kind. Years
> ago we had packagers trying to get their stuff in by using cpack.
> While it might be of some help for non official packages it was not
> really fit
El mié., 11 de jul. de 2018 07:33, Ian Jackson <
ijack...@chiark.greenend.org.uk> escribió:
> [snip]
I really don't agree with the thrust of Lisandro's comments. AFAICT
> what Lisandro is saying is this: because the upstream components may
> not always be perfect; and even may be totally
El mar., 10 de jul. de 2018 15:46, Kyle Edwards
escribió:
> On Tue, 2018-07-10 at 12:52 -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > Well, there are cases when upstream is doing things the right way
> > with respect to Debian but... what about derivatives (distributions
> > which base
Kyle Edwards writes ("Re: A message from CMake upstream: announcing dh-cmake"):
> I understand what you're saying. As a concrete example, we all know
> that Debian requires *.so library symlinks to live in the -dev package.
> But let's say there's a hypothetical Debian deriv
On Tue, 2018-07-10 at 12:52 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Well, there are cases when upstream is doing things the right way
> with respect to Debian but... what about derivatives (distributions
> which base themselves in Debian)? Sometimes they need something
> different, and
El viernes, 6 de julio de 2018 12:59:58 -03 Kyle Edwards escribió:
> On Thu, 2018-07-05 at 14:04 -0300, Lisandro Damián Nicanor Pérez Meyer
>
> wrote:
> > From what you write above I tend to think that simply by not using
> > dh-cmake whatever upstream has defined as packaging it will be simply
>
On Sat, 07 Jul 2018 00:25:15 +0200, Mattia Rizzolo wrote:
> On Fri, Jul 06, 2018 at 04:40:44PM -0400, Kyle Edwards wrote:
> > On Fri, 2018-07-06 at 21:00 +0100, Colin Watson wrote:
> > > If the libraries in question are DFSG-free themselves, there's no
> > > DFSG issue and you don't need to
On Sat, Jul 07, 2018 at 12:25:15AM +0200, Mattia Rizzolo wrote:
> On Fri, Jul 06, 2018 at 04:40:44PM -0400, Kyle Edwards wrote:
> > On Fri, 2018-07-06 at 21:00 +0100, Colin Watson wrote:
> > > If the libraries in question are DFSG-free themselves, there's no
> > > DFSG issue and you don't need to
On Fri, Jul 06, 2018 at 04:40:44PM -0400, Kyle Edwards wrote:
> On Fri, 2018-07-06 at 21:00 +0100, Colin Watson wrote:
> > If the libraries in question are DFSG-free themselves, there's no
> > DFSG issue and you don't need to remove them from the tarball (and
> > we'd generally encourage not
On Fri, 2018-07-06 at 21:00 +0100, Colin Watson wrote:
> If the libraries in question are DFSG-free themselves, there's no
> DFSG issue and you don't need to remove them from the tarball (and
> we'd generally encourage not modifying the upstream tarball
> unnecessarily for upload to Debian). The
On Fri, Jul 06, 2018 at 11:59:58AM -0400, Kyle Edwards wrote:
> I have a question about this (and I apologize if this is slightly off
> topic): VTK includes "convenience copies" of third-party libraries it
> uses to avoid "dependency hell", and also because we've made
> modifications to them that
On Thu, 2018-07-05 at 14:04 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> From what you write above I tend to think that simply by not using
> dh-cmake whatever upstream has defined as packaging it will be simply
> ignored (ie, it will become a "standard" CMake project).
Yes, this is true.
El jueves, 5 de julio de 2018 10:20:55 -03 Kyle Edwards escribió:
> Hi Lisandro,
>
> Thank you for expressing your concerns. You bring up some very valid
> points, and I will try to address all of them here.
[snip]
> > If upstream happens to be the Debian maintainer then *maybe* this
> > might
El jueves, 5 de julio de 2018 12:11:36 -03 Kyle Edwards escribió:
> So, to clarify: we've changed VTK to use GNUInstallDirs, which *itself*
> sets the proper directories for Debian, as I will explain below.
>
> On Thu, 2018-07-05 at 15:38 +0100, Simon McVittie wrote:
> > debhelper's
So, to clarify: we've changed VTK to use GNUInstallDirs, which *itself*
sets the proper directories for Debian, as I will explain below.
On Thu, 2018-07-05 at 15:38 +0100, Simon McVittie wrote:
> debhelper's Debian::Debhelper::BuildSystem::cmake already passes
>
On Thu, 05 Jul 2018 at 09:20:55 -0400, Kyle Edwards wrote:
> Our plan is to
> change VTK's upstream CMake scripts to make it more distro-friendly,
> then provide packaging scripts that take advantage of these changes.
> (We've already made some of these changes in the latest VTK master - it
> now
On Wed, 2018-07-04 at 11:30 +0200, Andreas Tille wrote:
> I think you can solve the lintian warning
> W: dh-cmake source: ancient-python-version-field x-python3-version
> 3.2
> by simply removing
> X-Python3-Version: >= 3.2
> from d/control.
Thanks for the tip, we will fix this in the next
Hi Lisandro,
Thank you for expressing your concerns. You bring up some very valid
points, and I will try to address all of them here.
On Wed, 2018-07-04 at 14:40 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> I even use it for 99% of my personal/job projects!
Glad to hear it!
> If
El martes, 3 de julio de 2018 16:56:42 -03 Kyle Edwards escribió:
> Hello everyone!
Hi Kyle!
> My name is Kyle. I work at Kitware, Inc., the upstream maintainer of
> the CMake buildsystem (https://www.cmake.org/) and VTK, the
> Visualization Toolkit (https://www.vtk.org/).
I'm Lisandro and,
Hi Kyle,
On Tue, Jul 03, 2018 at 03:56:42PM -0400, Kyle Edwards wrote:
> Hello everyone!
>
> My name is Kyle. I work at Kitware, Inc., the upstream maintainer of
> the CMake buildsystem (https://www.cmake.org/) and VTK, the
> Visualization Toolkit (https://www.vtk.org/). As some of you on the
>
On Wed, Jul 4, 2018 at 3:56 AM, Kyle Edwards wrote:
> Our end goal is to get both dh-cmake and VTK into Debian proper, but it
> is still in an experimental state, and there is still a lot of work to
> be done yet. We would like to get some feedback on dh-cmake, and we
> will eventually file a
Hello everyone!
My name is Kyle. I work at Kitware, Inc., the upstream maintainer of
the CMake buildsystem (https://www.cmake.org/) and VTK, the
Visualization Toolkit (https://www.vtk.org/). As some of you on the
Debian Science list may have heard, we are making an effort to
officially support
23 matches
Mail list logo
