<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hi Feri,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> If the memory isn't too tight, it should be possible to rebuild natively.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">My challenge is that I can't find <i>how</i> to build a 'development headers' version. I've tried
<a href="https://github.com/gonzalo/gphoto2-updater">this script</a> and “<a href="https://hyfrmn.wordpress.com/2015/02/03/install-libgphoto2-and-gphoto2-from-source-on-raspberry-pi/">Install libgphoto2 and gphoto2 from source on Raspberry Pi</a>” to roll my
own build, but those seem to leave me with a vanilla version, where I still need development headers for my downstream compatibility.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Is it something as silly as a switch I need to add to the 'make' step??<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> Debian "unstable" get more or less regular uploads when new upstream versions are released. These are migrated to "testing" a couple of days later (typically). A new Debian release means that "testing" is renamed to "stable", so
the version in the Debian stable release is frozen.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Are we talking cross purposes here? Are you talking about the OS while I’m talking about the app/package libgphoto-dev?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">When bullseye becomes the latest stable release for the Pi, past performance suggests it will only have one build of libgphoto-dev for its entire lifespan as the stable release.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">That’s the problem I’ve hit with buster, and I expect will hit again in 12-18 months when new cameras have been added to the libgphoto project, but without any updated builds of libgphoto-dev (or I can figure out how to DIY) it will
be trapped in February 2021 with the functionality from v2.5.27.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU">Regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU">Greig,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:EN-AU">0402 033 044.<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:EN-AU">-----Original Message-----<br>
From: Ferenc Wagner,,, <wferi@niif.hu> <br>
Sent: Wednesday, 6 October 2021 8:54 PM<br>
To: Greig Sheridan <gs@gisyd.com><br>
Cc: Ferenc Wagner,,, <wferi@niif.hu>; pkg-phototools-devel@lists.alioth.debian.org<br>
Subject: Re: [Pkg-phototools-devel] Upgrading ligbphoto2-dev on a Pi??</span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Greig Sheridan <<a href="mailto:gs@gisyd.com"><span style="color:windowtext;text-decoration:none">gs@gisyd.com</span></a>> writes:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> wferi wrote:<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">>> The libgphoto2 Debian package has a pretty standard build procedure,
<o:p></o:p></p>
<p class="MsoPlainText">>> but you probably lack the build environment for that.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> Sounds like it's complicated? If I can't cajole my install script into
<o:p></o:p></p>
<p class="MsoPlainText">> doing the build natively on a Pi then yeah, I'm going to need to rely
<o:p></o:p></p>
<p class="MsoPlainText">> on people like yourselves to keep it updated (for which I thank you).<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">If the memory isn't too tight, it should be possible to rebuild natively.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">>> It's actively maintained in Debian, but you apparently use the
<o:p></o:p></p>
<p class="MsoPlainText">>> version released in buster.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">> I've had a look around but I can only see the one release each for
<o:p></o:p></p>
<p class="MsoPlainText">> buster and stretch (unless previous ones have been removed)? As I
<o:p></o:p></p>
<p class="MsoPlainText">> understand it libgphoto gets a new release multiple times a year, but
<o:p></o:p></p>
<p class="MsoPlainText">> its 'development files' version is only updated with each major Debian
<o:p></o:p></p>
<p class="MsoPlainText">> release. If it only gets an update with each major o/s release it
<o:p></o:p></p>
<p class="MsoPlainText">> means I'm going to find myself in this same situation in a year or so.<o:p></o:p></p>
<p class="MsoPlainText">> Or am I missing something again?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Debian "unstable" get more or less regular uploads when new upstream versions are released. These are migrated to "testing" a couple of days later (typically). A new Debian release means that "testing" is renamed to "stable", so the
version in the Debian stable release is frozen.<o:p></o:p></p>
<p class="MsoPlainText">Bullseye is the current "stable", buster is "oldstable", stretch is "oldoldstable", and so on. So yes, stable releases get outdated eventually. See
<a href="https://backports.debian.org/"><span style="color:windowtext;text-decoration:none">https://backports.debian.org/</span></a> for a possible solution.<o:p></o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">Regards,<o:p></o:p></p>
<p class="MsoPlainText">Feri<o:p></o:p></p>
</div>
</body>
</html>