On Wed, Mar 11, 2026 at 07:48:30PM -0500, Dirk Eddelbuettel wrote:
>
> Charles,
>
> On 12 March 2026 at 09:09, Charles Plessy wrote:
> | Le Wed, Mar 11, 2026 at 08:39:13AM -0500, Dirk Eddelbuettel a écrit :
> | >
> | > Are you talking about exclusions such as the one r-base (updated today)
> has
> | > with respect to the JDK:
> |
> | for broader class exclusions we build-depend on packages that do not exist
> on
> | the given architectures.
> |
> | You just have to add "architecture-is-64-bit,
> architecture-is-little-endian" to
> | your build dependencies. The following commands can automate it for you.
> |
> | if ! grep -q architecture-is-64-bit debian/control ; then
> | cme modify dpkg-control 'source
> Build-Depends:.push("architecture-is-64-bit")'
> | fi
> |
> | if ! grep -q architecture-is-little-endian debian/control ; then
> | cme modify dpkg-control 'source
> Build-Depends:.push("architecture-is-little-endian")'
> | fi
>
> I have no idea what the command 'cme' is or does. I have never seen it
> before. From context this seems to imply some scripted way in which _you_
> modify debian/ files.
>
> Fine.
>
> Now assume that I do not use the same scripted solution. Is that ok?
>
>
> I had asked you very explicitly in the last email if you do this:
>
> > Could you illustrate with a diff against a representative package what you
> > mean here?
>
> but you chose to chop that part off.
>
> Can I ask again? As you have packages 'before' and 'after' your changes,
> could you possibly detail a change in a way I can comprehend?
Hi. Charles is just trying to make it easy to do the changes.
However, for simplicity, you can ignore completely the cme thing and
just consider what he said in plain English before those cme commands,
namely:
Add "architecture-is-64-bit, architecture-is-little-endian" to your build
dependencies.
The current Build-Depends for this package is like this:
Build-Depends: debhelper-compat (= 13), r-base-dev (>= 4.5.2), dh-r,
r-cran-codetools, r-cran-pkgkitten
so if we add those two packages to the Build-Depends, we get this:
Build-Depends: debhelper-compat (= 13), r-base-dev (>= 4.5.2), dh-r,
r-cran-codetools, r-cran-pkgkitten, architecture-is-64-bit,
architecture-is-little-endian
Is it more clear now?
(Note that at this point, with such a long build-depends line, many
people prefer to split the Build-Depends line into several lines, one
per build-dependency, so that adding and removing BD reflects
more clearly in diffs. If you are interested, the wrap-and-sort
command does that. I personally recommend that you take a look at it).
Thanks.
