DEPEND: Invalid atom (for reguire use flag)

[sebekk23]

Hi

I would like to make new package for Gentoo (MQTT explorer, just web client for now), i made my local repo according to guide that i found somewhere at gentoo wiki but my ebuild won't to digest/manifest.

Here is my ebuild:

Code: Select all

EAPI=8
DESCRIPTION="Web-based mqtt client"
HOMEPAGE="https://mqtt-explorer.com/"
SRC_URI="https://github.com/thomasnordquist/MQTT-Explorer/archive/refs/tags/v{PV}.zip"
LICENSE="CC-BY-NC-SA-4.0"
SLOT="0"
KEYWORDS="~amd64"
RDEPEND="
	>=net-libs/nodejs-24.11.1-r1[npm],
	>=sys-apps/yarn-1.22.22
"
DEPEND="${RDEPEND}"
DOC_CONTENTS="
	IMPORTANT: In production, use environment variables:
	export MQTT_EXPLORER_USERNAME=<username>
	export MQTT_EXPLORER_PASSWORD=<password>
"
src_unpack() {
	unpack "${A}"
}

Here is output of: ebuild mqtt-explorer-0.3.5.ebuild manifest unpack

Code: Select all

Error(s) in metadata for 'app-misc/mqtt-explorer-0.3.5':
  DEPEND: Invalid atom (>=net-libs/nodejs-24.11.1-r1[npm],), token 1
  RDEPEND: Invalid atom (>=net-libs/nodejs-24.11.1-r1[npm],), token 1

Mqtt explorer requires npm - so how can i mark it as required for this dependency(nodejs)?

[NeddySeagoon]

sebekk23,

Remove the comma (,) after the [npm]

Code: Select all

RDEPEND="
   >=net-libs/nodejs-24.11.1-r1[npm],

[sebekk23]

OMG it was it - thx

[sebekk23]

Next question about network sandbox - i've noticed that in live build(ebuild with 9999 version) downloading with i.e npm install works but in normal ebuild it doesn't.

How it(fetching node modules for app) should be done with normal ebuild? Should i prepare all node modules(in this case) in archive and place it somewhere publicly available?
As far as i know disabling network sandbox is worst idea ever - or maybe in this case it is worth to disable?


Ps.
Working npm install is used here sunshine-9999.ebuild and here rapydscript-ng-9999.ebuild

[NeddySeagoon]

sebekk23,

Disabling the network sandbox is a very bad idea. For a versioned (non-live) package.

Yes, you should package the required modules so that all the fetching can be done during the fetch phase.
As you know what you will be fetching, the tarball will appear in the manifest, with its size and hashes.

There is no need to make the tarball publicly available until you publish the ebuild.
For your own use, portage will find it if you put it into your distfiles directory, with all your other source downloads.
That's plenty good enough for your development.

Now the LICENSE= setting may get difficult, as you need to cite all the licenses that apply to all the modules you will be installing too.
Here be dragons.