distributions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Anna (cybertailor) Vyalkova" <cyber+gentoo@sysrq.in>
To: distributions@lists.linux.dev
Subject: Fwd: Detect QML Dependencies
Date: Fri, 31 Mar 2023 20:33:06 +0500	[thread overview]
Message-ID: <ZCb9MrFq5IbdnIZ-@sysrq.in> (raw)

[-- Attachment #0: Type: message/rfc822, Size: 66123 bytes --]

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


in Debian we package more and more QML applications and face the problem, that 
we don't have tooling to easily get a list of QML dependencies out of the qml 
files. I normally end up doing a grep in the qml files and than I need to 
translate these dependencies to the corresponding Debian packages. What is 
quite error prune.
Does anyone have already a working solution to detect the QML dependencies - 
maybe there is alaready a qmllinter/qmlchecker tool that returns the needed 
QML dependencies and create package dependencies?

That is currently my way:

grep -r --include="*qml" '^import ' | sed 's/^.*\.qml:import \([^ ]*.*\)/\1/g' 
| sort | uniq



[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-03-31 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 15:33 Anna (cybertailor) Vyalkova [this message]
2023-03-31 16:00 ` Detect QML Dependencies Neal Gompa

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:

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

  git send-email \
    --in-reply-to=ZCb9MrFq5IbdnIZ-@sysrq.in \
    --to=cyber+gentoo@sysrq.in \
    --cc=distributions@lists.linux.dev \


* 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;
as well as URLs for NNTP newsgroup(s).