public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Simone Weiß' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Bitbake.conf in isar and linting
Date: Wed, 20 Aug 2025 04:52:57 -0700 (PDT)	[thread overview]
Message-ID: <b2cf3b00-12df-4d6a-9a0a-380ff95a43afn@googlegroups.com> (raw)
In-Reply-To: <AS4PR10MB531881491F2C8A8579B95A14ED33A@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 2185 bytes --]

Hi I see thanks,

While oelint-adv is fairly configurable, I see another point here: Is it 
really advisable to hard code paths such as /etc, /usr/bin, bin and so on? 
I only noticed that those are hard-coded by running oelint-adv, If a distro 
(also in different versions I believe there was some switch with debian 
12(merged usr))
however handles bin usr etc differently then other it would be nice to 
configure them in variables.

Simone

On Wednesday, August 20, 2025 at 7:40:55 AM UTC+2 Schmidt, Adriaan wrote:

> Moessbauer, Felix (FT RPD CED OES-DE), Dienstag, 12. August 2025 11:10:
> > On Mon, 2025-08-11 at 23:44 -0700, 'Simone Weiß' via isar-users wrote:
> > > Hey,
> > >
> > > 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.
> > 
> > Hi,
> > 
> > let's loop Adriaan Schmidt in, as he already worked on an ISAR linter.
>
> 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.
>
> Adriaan
>
> > Felix
> > 
> > >
> > > Is there a specific reason why isars bitbake.conf would omit to also
> > > define variables got etc, bin and friends?
> > >
> > >
> > > Best,
> > > Simone
> > 
> > --
> > Siemens AG
> > Linux Expert Center
> > Friedrich-Ludwig-Bauer-Str. 3
> > 85748 Garching, Germany
>
>

-- 
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/b2cf3b00-12df-4d6a-9a0a-380ff95a43afn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2933 bytes --]

  reply	other threads:[~2025-08-20 12:42 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 [this message]
2025-08-20 13:07     ` Baurzhan Ismagulov
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=b2cf3b00-12df-4d6a-9a0a-380ff95a43afn@googlegroups.com \
    --to=isar-users@googlegroups.com \
    --cc=simone.weiss@elektrobit.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