Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] snapper: add recipe
Date: Sun, 20 Oct 2024 06:00:28 +0200	[thread overview]
Message-ID: <S4ZMLS.LVMSY47J6K89@t-online.de> (raw)
In-Reply-To: <CAMKF1sopLEXWs+9GuF5rE=o+cThN01X0-0xkiAafVsXNWnb2Ng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4522 bytes --]

The problem has already been fixed in Alpine Linux. Added a patch found 
there

Additionally, I also added dependencies for e2fsprogs and ncurses, 
since snapper links to -ltinfo and a runtime dependency of 
util-linux-mount

On Sat, Oct 19 2024 at 06:40:56 PM -07:00:00, Khem Raj 
<raj.khem@gmail.com> wrote:
> On Fri, Oct 18, 2024 at 9:23 AM Khem Raj <raj.khem@gmail.com 
> <mailto:raj.khem@gmail.com>> wrote:
>> 
>>  On Fri, Oct 18, 2024 at 6:15 AM Markus Volk via 
>> lists.openembedded.org
>>  <f_l_k=t-online.de@lists.openembedded.org 
>> <mailto:f_l_k=t-online.de@lists.openembedded.org>> wrote:
>>  >
>>  > Snapper is a tool for Linux file system snapshot management. 
>> Apart from
>>  > the obvious creation and deletion of snapshots it can compare 
>> snapshots
>>  > and revert differences between them. In simple terms, this allows 
>> root
>>  > and non-root users to view older versions of files and revert 
>> changes.
>>  >
>>  > Signed-off-by: Markus Volk <f_l_k@t-online.de 
>> <mailto:f_l_k@t-online.de>>
>>  > ---
>>  >  .../recipes-support/snapper/snapper_0.11.2.bb | 35 
>> +++++++++++++++++++
>>  >  1 file changed, 35 insertions(+)
>>  >  create mode 100644 
>> meta-oe/recipes-support/snapper/snapper_0.11.2.bb
>>  >
>>  > diff --git a/meta-oe/recipes-support/snapper/snapper_0.11.2.bb 
>> b/meta-oe/recipes-support/snapper/snapper_0.11.2.bb
>>  > new file mode 100644
>>  > index 000000000..2759cdafb
>>  > --- /dev/null
>>  > +++ b/meta-oe/recipes-support/snapper/snapper_0.11.2.bb
>>  > @@ -0,0 +1,35 @@
>>  > +SUMMARY = "Snapper is a tool for Linux file system snapshot 
>> management"
>>  > +HOMEPAGE = "<https://github.com/openSUSE/snapper>"
>>  > +LICENSE = "GPL-2.0-only"
>>  > +LIC_FILES_CHKSUM = 
>> "file://COPYING;md5=751419260aa954499f7abaabaa882bbe" 
>> <file://copying;md5=751419260aa954499f7abaabaa882bbe/>
>>  > +
>>  > +DEPENDS = "acl boost btrfs-tools dbus json-c libxml2 lvm2 zlib"
>>  > +
>>  > +# Build separation is slightly broken
>>  > +inherit autotools-brokensep pkgconfig gettext
>>  > +
>>  > +SRC_URI = 
>> "git://github.com/openSUSE/snapper.git;protocol=https;branch=master"
>>  > +SRCREV = "6c603565f36e9996d85045c8012cd04aba5f3708"
>>  > +
>>  > +S = "${WORKDIR}/git"
>>  > +
>>  > +PACKAGECONFIG ?= "${@bb.utils.filter 
>> <mailto:${@bb.utils.filter>('DISTRO_FEATURES', 'api-documentation 
>> systemd pam', d)}"
>>  > +PACKAGECONFIG[pam] = "--enable-pam,--disable-pam,libpam"
>>  > +PACKAGECONFIG[systemd] = "--enable-systemd,--disable-systemd"
>>  > +PACKAGECONFIG[api-documentation] = 
>> "--enable-doc,--disable-doc,libxslt-native 
>> docbook-xsl-stylesheets-native"
>>  > +
>>  > +# Avoid HOSTTOOLS path in binaries
>>  > +export DIFFBIN="${bindir}/diff"
>>  > +export RMBIN = "${bindir}/rm"
>>  > +export TOUCHBIN = "${bindir}/touch"
>>  > +export CPBIN = "${bindir}/cp"
>>  > +
>>  > +
>>  > +do_install:append() {
>>  > +       install -d ${D}${sysconfdir}/sysconfig
>>  > +       install -m0644 ${S}/data/default-config 
>> ${D}${sysconfdir}/sysconfig/snapper
>>  > +}
>>  > +
>>  > +FILES:${PN} += "${libdir}/pam_snapper ${libdir}/systemd 
>> ${libdir}/zypp ${libdir}/security ${datadir}"
>>  > +# bash is needed for the testsuite
>>  > +RDEPENDS:${PN} = "bash diffutils util-linux"
>> 
>>  It would be good to package test binary and resources into 
>> ${PN}-ptest package
>>  and then attach the needed rdeps to ${PN}-ptest package also look 
>> into
>>  inheriting
>>  ptest class which should provide a basic build block for adding 
>> ptests.
>> 
> 
> it fails to build with musl see
> <https://errors.yoctoproject.org/Errors/Details/809996/>
> 
> stavfs64 is not needed if we are already using LFS64, we can just use
> statvfs even on glibc
> otherwise add -D_LARGEFILE64_SOURCE with musl builds to cflags
> 
>>  > --
>>  > 2.47.0
>>  >
>>  >
>>  > -=-=-=-=-=-=-=-=-=-=-=-
>>  > Links: You receive all messages sent to this group.
>>  > View/Reply Online (#112978): 
>> <https://lists.openembedded.org/g/openembedded-devel/message/112978>
>>  > Mute This Topic: 
>> <https://lists.openembedded.org/mt/109081580/1997914>
>>  > Group Owner: openembedded-devel+owner@lists.openembedded.org 
>> <mailto:openembedded-devel+owner@lists.openembedded.org>
>>  > Unsubscribe: 
>> <https://lists.openembedded.org/g/openembedded-devel/unsub> 
>> [raj.khem@gmail.com <mailto:raj.khem@gmail.com>]
>>  > -=-=-=-=-=-=-=-=-=-=-=-
>>  >


[-- Attachment #2: Type: text/html, Size: 5026 bytes --]

  reply	other threads:[~2024-10-20  3:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 13:17 [meta-oe][PATCH] snapper: add recipe Markus Volk
2024-10-18 16:23 ` [oe] " Khem Raj
2024-10-20  1:40   ` Khem Raj
2024-10-20  4:00     ` Markus Volk [this message]
     [not found] <17FF8E6016EB1E66.8839@lists.openembedded.org>
2024-10-18 13:18 ` Markus Volk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=S4ZMLS.LVMSY47J6K89@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox