›

Installation, Linux distro variants

dick_freebirddick_freebird
in General

Pulling latest installs for Win & Linux I noticed that there are
several different Linux distros on the list (but far from all).

Me, I started (this time around) with Ubuntu but I have been
setting up newer machines with Debian, then Mint, and now
looking to move over to another Debian variant that has a
more "classic / lightweight" (like boot to console, and fvwm
when you ask for it, UX) by the name of Devuan.

Wondering why any proliferation of Linux builds at all, and
if "reasons", how to know or at least guess smart about
which one. I would guess Ubuntu for the Debian derived,
CentOS for anyone still throwing money at Red Hat or using
the "enterprise" features (whatever those are - I left Rad Hat
the first time a "sure, go ahead" mass update bricked the
system). What Suse is there for, or what others it might cover,
dunno.

Others might find a little README about that, useful once.

Comments

  • MatthiasMatthias

    Hi @dick_freebird,

    you mean Ubuntu .deb package can be used on Debian for example? I'm not sure, honestly I have never tried. I'd not be entirely surprised as dependencies become increasingly generic. But I'd not bet at it.

    People already discussed generic packages such as FlatPak, but frankly I did not have the energy yet to look into how to build them. I guess eventually deployment will boil down to something like that and there will be no distro specific packages anymore.

    Matthias

  • dick_freebirddick_freebird

    Right, the "package managers" seem to want -their-
    style (though I don't rightly know whether (say) Red Hat
    "rpm" would do the right thing if you pointed it at a Debian
    .deb - I just try to pull the ones they say is "their format").

  • sebastiansebastian

    The automatically built Ubuntu .deb is not compatible with debian (stable), as usually their releases are too far apart and they use some different package names (it can happen that they are if their releases of the LTS versions are only a couple of months apart, but that's the exception not rule). It's not hard to build for debian though.

    Here's my addition for debian12 (bookworm) (scripts/makedeb.sh, line 33):

    debian12)
  depends="python3-dev, libc6-dev, libgcc-s1, libqt6core5compat6, libqt6designer6, libqt6gui6, libqt6multimedia6, libqt6multimediaquick6, libqt6network6, libqt6printsupport6, libqt6sql6, libqt6svg6, libqt6widgets6, libqt6xml6, libruby3.1, libstdc++6, zlib1g"
  ;;

    Additionally change the build.sh command in the same file to use all available cores to compile (line 65):

    # do the actual build
./build.sh -j$(nproc) \
           -bin $bininstdir \
           -build $builddir \
           -rpath /$libdir

    This has served me well to build quite quickly (with ccache installed). Just checkout the latest tag (as of writing) git checkout v0.28.10 and then run ./script/makedeb.sh debian12. After build you can install the newly built deb with sudo apt install ./klayout_0.28.10-1_amd64.deb

  • MatthiasMatthias

    @sebastian Thanks a lot for this update! I personally rarely use all cores for building as I have other interesting things to do in parallel :)

    But I wonder if Qt6 is mainstream on Debian now?

    It's not very difficult to set up Debian as an additional standard target. In the end I try to avoid inflation of builds. But I would sacrifice older Ubuntu's in favor of Debian. What's your suggestion?

    Matthias

  • dick_freebirddick_freebird

    If I had a good "Make" setup I would do
    the compile but I depend on spoon feeding
    for that, I do not comprehend all the low
    level setup stuff I see.

    My interests include long term archival of
    design tools alongside chip designs and
    I am suspicious that .deb packages will
    "break" for stale dependencies, earlier
    than a compile-from-pile (having all the
    dependencies also archived) would as
    distros "age out".

Sign In or Register to comment.
Powered by Vanilla