Skip to content

Adding reMarkdown to vellum#302

Open
esclee wants to merge 5 commits into
vellum-dev:mainfrom
esclee:main
Open

Adding reMarkdown to vellum#302
esclee wants to merge 5 commits into
vellum-dev:mainfrom
esclee:main

Conversation

@esclee

@esclee esclee commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Adding reMarkdown to vellum

@rmitchellscott

Copy link
Copy Markdown
Member

/publish-testing

maintainer="esclee <[email protected]>"
pkgname=remarkdown
pkgver=0.1.0
pkgrel=1

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
pkgrel=1
pkgrel=0

@github-actions

Copy link
Copy Markdown

Packages published to testing repo:

  • reMarkdown

Install with:

vellum add reMarkdown@testing

Comment on lines +19 to +24
unpack() {
case "$CARCH" in
aarch64) unzip -o "$srcdir"/reMarkdown-arm64-$pkgver.zip -d "$srcdir"/rmd ;;
armv7) unzip -o "$srcdir"/reMarkdown-armv7h-$pkgver.zip -d "$srcdir"/rmd ;;
esac
}

@Eeems Eeems Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this just appears to be unifying the directory it unpacks to, is it really worth it to override extract instead of just doing a cd to the correct location in package?

Comment on lines +34 to +40
postinstall() {
echo ""
echo "=================================================="
echo " NOTE: To use reMarkdown, you must refresh AppLoad"
echo "=================================================="
echo ""
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rmitchellscott we keep on having packages all duplicate this message all over the place, which results in multiple instances of this message if you install more than one application. Is is something we really care to present to users this way via vellum? Especially now that there is more than one launcher?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with removing these messages, as we don't notify that xovi needs to be restarted for every QMD, etc.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, I can open a PR to clean up all the other packages. Ideally we work on using triggers in packages to unify messages like this, or better yet, trigger the reload with them instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants