From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Bitbake.conf in isar and linting
Date: Wed, 20 Aug 2025 15:07:52 +0200 [thread overview]
Message-ID: <aKXIqAKlHsQqM-NN@abai.de> (raw)
In-Reply-To: <AS4PR10MB531881491F2C8A8579B95A14ED33A@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>
On 2025-08-20 05:40, 'Schmidt, Adriaan' via isar-users wrote:
> > > I am wondering if a specific styleguide exists for isar? Normally for
> > > bitbake based projects I am using oelint-adv.
> > >
> > > When I played around with dpkg-raw and wanted to install some file
> > > under /etc, this caused the linker to complain about not using
> > > sysconfdir for etc.
>
> Well, yes and no...
> Years ago I very briefly looked into technical solutions for bitbake linting (maybe it was oelint-adv, but I don't exactly remember), and how flexible/extensible those might be.
> Even with that in place, it would be up to the Isar Community to actually define a style and rules, but as far as I'm aware nothing like this exists yet.
>
> > > Is there a specific reason why isars bitbake.conf would omit to also
> > > define variables got etc, bin and friends?
We've looked at pylint but not at oelint-adv.
Ideally, we imagined our recipes as three-liners (inherit dpkg, SRC_URI, SRCREV
or similar) which wouldn't require much of style. In the (very distant) future,
we'd need automatically created recipes or even not need recipes at all (all
necessary metadata is already inside the Debian-style source packages). This
not being the case today :) , I think oelint-adv could be evaluated whether
it's useful and configurable enough for Isar. Experiences welcome.
Regarding your specific questions -- sysconfdir, etc, bin and friends -- those
vars are very OE-specific and in are in case of Isar all managed by the Debian
package building infrastructure. So my wish would be exactly about it -- if the
tool turns to be useful for Isar, we shouldn't force people to deal with many
false positives.
Other than that, seems that the tool is not intended to provide pure formatting
guidance, but also real style guidance -- in that case, I think major effort
would be needed to make it useful to check for Isar development patterns.
With kind regards,
Baurzhan
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/aKXIqAKlHsQqM-NN%40abai.de.
next prev parent reply other threads:[~2025-08-20 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 6:44 'Simone Weiß' via isar-users
2025-08-12 9:09 ` 'MOESSBAUER, Felix' via isar-users
2025-08-19 7:15 ` 'Simone Weiß' via isar-users
2025-08-20 5:40 ` 'Schmidt, Adriaan' via isar-users
2025-08-20 11:52 ` 'Simone Weiß' via isar-users
2025-08-20 13:07 ` Baurzhan Ismagulov [this message]
2025-08-21 9:16 ` 'Weiß, Simone' via isar-users
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=aKXIqAKlHsQqM-NN@abai.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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