ackages were upgraded.
> >>
> >>
> >> The installation script attempts to execute the following command:
> >>
> >> /usr/bin/mkdir -p '/usr/local/share/man/man3'
> >>
> >> Is there a solution how I can solve the problem in the PKGBU
occurred, no packages were upgraded.
>
>
> The installation script attempts to execute the following command:
>
> /usr/bin/mkdir -p '/usr/local/share/man/man3'
>
> Is there a solution how I can solve the problem in the PKGBUILD?
>
>
> Thank you in advance!
> Klaus.
ng command:
/usr/bin/mkdir -p '/usr/local/share/man/man3'
Is there a solution how I can solve the problem in the PKGBUILD?
Thank you in advance!
Klaus.
https://wiki.archlinux.org/title/Arch_package_guidelines#Package_etiquette
First point. You should not be installing to /usr/lo
filesystem (owned by
filesystem)
Errors occurred, no packages were upgraded.
The installation script attempts to execute the following command:
/usr/bin/mkdir -p '/usr/local/share/man/man3'
Is there a solution how I can solve the problem in the PKGBUILD?
Thank you in advance!
Klau
occurred, no packages were upgraded.
The installation script attempts to execute the following command:
/usr/bin/mkdir -p '/usr/local/share/man/man3'
Is there a solution how I can solve the problem in the PKGBUILD?
Thank you in advance!
Klaus.
--
-std-move.patch
I'd appreciate thoughts on anything else I should fix in the PKGBUILD. I am
also unclear whether I should list debugedit as a build dependency -- it being
somewhat of a generic dependency to the makepkg process. Should it be included
as well?
(note: this is a BIG build an
te it if you paste the PKGBUILD into the email body, and not
> attach it. Would also make it easier to quote.
Here is the updated PKGBUILD:
--8<---cut here---start->8---
# Maintainer: Jonas Serych
pkgname='powertabeditor'
pkgver='2.0
On 19-02-2024 10:39, Jonas Serych wrote:
The PKGBUILD got sent as a binary mime type, sorry about that. Here it
is as text/plain.
One comment :
upstream readme mnetrions requiring a 'midi sequencer' .
Some soundcards offer that ability in hardware, but the majority doesn&#x
The PKGBUILD got sent as a binary mime type, sorry about that. Here it
is as text/plain.
# Maintainer: Jonas Serych
pkgname='powertabeditor'
pkgver='2.0.0_alpha19'
pkgrel=1
pkgdesc="Guitar tablature viewer and editor"
arch=('x86_64')
url="https:/
Hi,
this is my first time creating a PKGBUILD. I tried to follow the
guidelines and the recommended practices for cmake packages, but not
sure I didn't miss something. Thanks for any suggestions.
I checked that it builds in clean chroot. The software seems to work
well, except for JACK s
On 1/8/24 17:52, Doug Newgard wrote:
r(commit count).g(commit)
but that is about the best I was able to work out. If you know some
additional cmake magic I missed that allows grabbing the name from one of the
generated files in a format better than that above, you will have to help me
with it
On Mon, 8 Jan 2024 16:56:16 -0600
"David C. Rankin" wrote:
>There is no way to pull from the internal CPACK name to get precisely the
> CPACK_PACKAGE_VERSION out of it. You also cannot simply add a "TZST"
> generator and then either "cmake --build . --target package" or "make
> package" to u
enerated
files in a format better than that above, you will have to help me with it, I
couldn't find it.
With all the changes, and removing ${srcdir} from my circa 2009 PKGBUILD
go-by, the PKGBUILD is now quite tidy:
pkgname=wiringx-git
_gitname=wiringX
pkgver=251.54030cd
pkgrel
On 1/7/24 08:37, Doug Newgard wrote:
If there is
ever an actual "Release" of wiringX, then we can remove the pkgver() function
entirely.
That's not how -git PKGBUILDs work. It builds from HEAD and should always build
from HEAD. You really need to fix the pkgver function. Looking at the upstream
> If there is
> ever an actual "Release" of wiringX, then we can remove the pkgver() function
> entirely.
That's not how -git PKGBUILDs work. It builds from HEAD and should always build
from HEAD. You really need to fix the pkgver function. Looking at the upstream
CMakeLists.txt, I would version
already done by makepkg and I'm pretty sure
cmake will produce its own output that make outputting "Cmake..." redundant.
Otherwise, this looks like a pretty solid PKGBUILD to me! Make sure the use
namcap on the PKGBUILD and the built .pkg(.tar.zst)
[1]: https://wiki.archlinux.org/tit
On 1/6/24 11:36, Doug Newgard wrote:
mv "$pkgdir/usr/local/"* "$pkgdir/usr"
rm -r "$pkgdir/usr/local"
Can you not set a prefix? This step should not normally necessary.
Yes it can,
I was reading the cmake documentation wrong:
build() {
cd "${srcdir}/$_gitname/build"
cmake -DCMA
On 1/6/24 11:36, Doug Newgard wrote:
url="httpx://wiringx.org/"
Typo
fat-fingers
pkgver() {
cd "${srcdir}/$_gitname"
echo $(git rev-list --count HEAD).$(git rev-parse --short HEAD)
}
This will cause problems if there is ever a release. See
https://wiki.archlinux.org/title/VCS_pack
s TINY (oh, tiny...)
Having a one file package and another 3-file package (plus the LICENSE) just
didn't seem like a good use of space.
I'll finish going through all comments, incorporating the changes, build
and then repost the PKGBUILD of another review.
--
David C. Rankin, J.D.,P.E.
In addition to things others have said.
> url="httpx://wiringx.org/"
Typo
> pkgver() {
>cd "${srcdir}/$_gitname"
>echo $(git rev-list --count HEAD).$(git rev-parse --short HEAD)
> }
This will cause problems if there is ever a release. See
https://wiki.archlinux.org/title/VCS_package_gui
Hi,
According to manual.wiringx.org , wiringX is only a library and nothing
else. I don't think the splitting into two packages part applies here,
as there is nothing to install other than the library.
--
Cheers,
Aᴀʀᴏɴ
OpenPGP_0x4E85967FC7C436BE.asc
Description: OpenPGP public key
OpenPG
You might also want to look at the CMake package guidelines [1]. In
particular, cmake should be called from build(), not prepare().
[1] https://wiki.archlinux.org/title/CMake_package_guidelines
signature.asc
Description: PGP signature
On 1/6/24 01:22, Jean-Claude wrote:
In addition to what has been said, do not include the package name in
the description in a self-referencing way.[1]
[1] https://wiki.archlinux.org/title/Arch_package_guidelines#Package_etiquette
Thanks Aaron and Jean-Claude,
I'll fix those items and put i
In addition to what has been said, do not include the package name in
the description in a self-referencing way.[1]
[1] https://wiki.archlinux.org/title/Arch_package_guidelines#Package_etiquette
signature.asc
Description: PGP signature
;m pretty sure cmake will produce its own output that make
outputting "Cmake..." redundant.
Otherwise, this looks like a pretty solid PKGBUILD to me! Make sure the
use namcap on the PKGBUILD and the built .pkg(.tar.zst)
[1]: https://wiki.archlinux.org/title/Arch_packa
All,
I'm thinking of adding a wiringX-git package to AUR and wanted to put the
PKGBUILD out for comment and help. It's a simple tiny package used for
embedded development to manipulate GPIO pins.
What I've cobbled together is:
pkgname=wiringX-git
_gitname=wiringX
pkg
Le 21/10/2023 à 14:48, Lone_Wolf a écrit :
On 21-10-2023 10:05, Robin Candau wrote:
As such, a package specifically made for derivatives (like this one,
made to be used with the runit init system) is not allowed on the AUR.
On the other hand runit is available from aur and archwiki describr
On 21-10-2023 10:05, Robin Candau wrote:
As such, a package specifically made for derivatives (like this one,
made to be used with the runit init system) is not allowed on the AUR.
On the other hand runit is available from aur and archwiki describres
how to use it alongside systemd .
Eri
Le 21/10/2023 à 00:39, Eric a écrit :
Hi all,
Hi Eric!
I'm working on this PKGBUILD to provide a displaylink-runit service. I
use an Artix based distro using runit instead of systemD as the init system.
Before I publish this, please review this. [...]
The AUR is meant for Arch Linux
Hi all,
I'm working on this PKGBUILD to provide a displaylink-runit service. I use
an Artix based distro using runit instead of systemD as the init system.
Before I publish this, please review this. I have posted the link to my PR
to a few Linux communities and I have addressed their com
update your email address in the PKGBUILD.
Anyway, you /could/ have multiple emails in the PKGBUILD but the idea
here is mostly to have a way to contact you directly if you're not
responding to comments on the package's AUR webpage. One email address
is fine :)
2) AUR packages are c
Hey Ross!
> Hey and hello, new here, and am wondering how to submit a patch to a
> file... specifically the PKGBUILD for the package pissircd-git -- I've been
> copying my own PKGBUILD file over during the generation of a package build
> to avoid having it try to create a socke
Hey and hello, new here, and am wondering how to submit a patch to a
file... specifically the PKGBUILD for the package pissircd-git -- I've been
copying my own PKGBUILD file over during the generation of a package build
to avoid having it try to create a socket file in my home directory.
repo you're trying to build (notice how "source" and
"build" are written in /italic/ in the wiki [1], indicating that they
have to be adapted to your case).
Also, you have to `cd` first to the cloned repo before launching build
instructions.
Finally, "libadwa
/Transferring OP's reply to the proper mailing list/.
On Sun, Jul 2, 2023 at 6:59 PM Robin Candau wrote:
Le 02/07/2023 à 04:20, james smith a écrit :
I am trying to package this https://github.com/lemmygtk/lemoa
this is my pkgbuild any tips on how to improve it before I
Also, the proper mailing list to ask for a PKGBUILD review is
aur-general@lists.archlinux.org.
I haven't noticed you used aur-...@lists.archlinux.org instead when I
replied the first time so I forwarded the discussion to the proper
mailing list this time via this reply.
Let's con
On Wed, 22 Mar 2023 07:55:44 -0300
jamil bio wrote:
> Hello!
>
> I would like to introduce my project to the AUR mailing list. I am about to
> upload a PKGBUILD of a `datediff.sh' script which does calendrical
> calculations with shell built-ins, and has got some other few
On 2023-03-22 at 08:33:59 -0300,
jamil bio wrote:
> > md5 is broken and should not be used, sha256 or similar would be advised.
>
> Will use other checksum algos... Will switch to sha1. Thanks!
SHA1 is broken. As indicated, please use SHA256 (or even SHA512).
> On 22/03/2023 08:16, Martin Rys
> Adding the extension to the executable is non-standard,
Indeed Hroptatyr's 'C-code datediff' already exists in community as
'dateutils'. It is not desirable to install the datediff.sh script as
'datediff' to avoid such instance of conflict.. However, what binary name would
be cool to install
AUR mailing list. I am about to
> upload a PKGBUILD of a `datediff.sh' script which does calendrical
> calculations with shell built-ins, and has got some other few functions as
> well.
>
> Would installing the script as `datediff.sh' to /usr/bin be standard?
>
>
That last e-mail encoding looks borked on my mailing list reader (the
terminal), so I am sending the PKGBUILD again.
# Maintainer: Jamil SN
pkgname='datediff.sh'
pkgbase='shellDatediff'
pkgver=0.23.4
pkgrel=1
#epoch=
pkgdesc='Calculate time differences with Ksh, Bash
Hello!
I would like to introduce my project to the AUR mailing list. I am about to
upload a PKGBUILD of a `datediff.sh' script which does calendrical calculations
with shell built-ins, and has got some other few functions as well.
Would installing the script as `datediff.sh' to /
On Mon, Jan 9, 2023 at 4:34 PM Frederick Zhang
wrote:
> > -DCMAKE_BUILD_TYPE='None' \
>
> Shouldn't this be Release or RelWithDebInfo? [3]
>
> PS: You don't have to send emails in both plaintext and HTML here.
>
> [1] https://wiki.archlinux.org/title/VCS_package_guidelines
> [2] https
On 9/1/23 23:57, Robin Candau wrote:
Not necessarily. If the package has an official website, it should be
used in the URL var instead of the repo.
So in this case, the URL should contain the official website URL of the
package [1] and the source array should contain the GitHub repo [2].
On 10
Le 09/01/2023 à 13:48, Frederick Zhang a écrit :
> And I just realised:
>
>> url="https://github.com/wakatime/$pkgname";
>> source=("git+https://github.com/Tatsh/kate-wakatime";)
>
> I think it's better to use the same repository for URL and source.
Not necessarily. If the package has an offici
https://github.com/Tatsh/kate-wakatime
[3] https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html
On 9/1/23 23:14, Sharafat Karim wrote:
Hi there,
I'm writing to request that my PKGBUILD for /kate-wakatime/ be added to the
Arch User Repository (AUR). I have tested the PKGBUILD
Le 09/01/2023 à 13:14, Sharafat Karim a écrit :
> Hi there,
Hi!
> I'm writing to request that my PKGBUILD for kate-wakatime be added to the
> Arch User Repository (AUR). I have tested the PKGBUILD and it works as
> expected. But I'm unsure about this script's f
or RelWithDebInfo? [3]
PS: You don't have to send emails in both plaintext and HTML here.
[1] https://wiki.archlinux.org/title/VCS_package_guidelines
[2] https://github.com/Tatsh/kate-wakatime
[3] https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html
On 9/1/23 23:14, Sharafat Kar
Hi there,
I'm writing to request that my PKGBUILD for *kate-wakatime* be added to the
Arch User Repository (AUR). I have tested the PKGBUILD and it works as
expected. But I'm unsure about this script's formatting or other checkups.
I'll really appreciate any advice.
Bert, et al.,
> The general method is to keep the automation not in the repository
> (path) where the PKGBUILD and .SRCINFO reside. aurpublish[1] for
> example helps you set up a single source repository. Any packaging
> utilities can live in the repository root while subfolders
how do people who have some automated process (like me with my
Makefile)
to produce PKGBUILD and .SRCINFO typically deal with this, structure
things? (i don't *think* i saw any mention of this in the various wiki
pages; apologies if i missed something.)
The general method is to kee
hi, Caleb,
thanks very much.
> Hence almost all the PKGBUILD files in Arch official repos and the AUR
> have override build system defaults from source packages to set the
> prefix to be appropriate for package-manager managed paths rather than
> end user source installs.
thanks.
id /usr/local is not where the system package
manager should ever put anything. Distro managed packages should always
be in /usr and so forth.
Hence almost all the PKGBUILD files in Arch official repos and the AUR
have override build system defaults from source packages to set the
prefix to be app
Doug,
thanks for the reply.
> The only real issue I see is using $pkgdir in the build function. It's
> not well defined at that point, and should not be relied on. Using
> that as a prefix doesn't really make sense anyway, prefix is for the
> install location, such as /usr/ or /opt/$pkgname/.
ah
On Wed, 21 Dec 2022 22:38:29 +0300
Greg Minshall wrote:
> hi. i'm trying to submit my first package to AUR. my package files are
> here:
>
> https://git.sr.ht/~minshall/aur-orgtbl-query/tree
>
>
> if anyone has a chance to look over my PKGBUILD (and any
hi. i'm trying to submit my first package to AUR. my package files are
here:
https://git.sr.ht/~minshall/aur-orgtbl-query/tree
if anyone has a chance to look over my PKGBUILD (and any other of the
files), and has any comments, i'm all ears.
cheers, Greg
Fabio,
a newbie question:
> there is validpgpkeys but is not checked in source=()
would that suggest changing
source=("git+https://gitlab.com/minecraftchest1/steamdeck-file-share-tool#tag=$pkgver";)
to something like this
source=("git+https://gitlab.com/minecraftchest1/steamdeck-f
cd "${srcdir}"
install -Dm 755 "bin/${pkgname}.sh" "${pkgdir}/usr/bin/${pkgname}"
}
Changes:
- Deleted every empty/not used variables to make the PKGBUILD more readable.
- Deleted 'sed' and 'bash' from the "depends" array. Indeed
Hello,
> please install the script as file-sharing-tool (without .sh)
This is not always needed, it depends on how you want it to be, for
example "acme.sh" keeps the .sh due to the naming they wanted.
However it is PREFERED to use a shebang to the interpreter needed to run
the script on the
Il 12/12/22 19:03, Wyatt C Jackson ha scritto:
I recently put together a PKGBUILD file for a tool I made and want to put on
the AUR. While I believe it should be fine, I would like to have it reviewed
before I upload it.
---
```
# Maintainer: Minecraftchest1
pkgname=file-sharing-tool
pkgver
Hello,
This looks good to me, however I advice to omit any opinions which you
have not defined.
Apart from that it looks good, make sure to build and install the
package to ensure everything is working fine, follow the following:
https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I recently put together a PKGBUILD file for a tool I made and want to put on
the AUR. While I believe it should be fine, I would like to have it reviewed
before I upload it.
- ---
```
# Maintainer: Minecraftchest1
pkgname=file-sharing-tool
Georg, Polarian, and kpcyrd,
thanks much! that's what made sense.
cheers, Greg
On 12/12/22 07:31, Greg Minshall wrote:
hi. i am putting together a PKGBUILD. there are certain dependencies
required for cutting a release, rolling a version, etc. but, for just
downloading the sources and building, these dependencies are not needed.
can i leave dependencies *out* of
branch.
Whichever PKGBUILD you are making, you should specify ALL dependencies
needed at the different stages, you can specify whether a dependency is
needed just to build the package (such as a C compiler if the codebase
is in C), and then the packages needed for the program to run, this is
simpler: in my PKGBUILD, do i need to list in any of the *depends any
package that will *not* be used by makepkg? (motivation: the makefile
in my package has uses other than building the package, and for some of
*those* uses -- such a rolling a rev, etc. -- *do* need other
packages
hi, mpan,
> Hello. makepkg does not support chosing between different
> configurations. One PKGBUILD, one build type. If multiple build
> configurations are needed, write (or generate) multiple PKGBUILDs.
thanks for the reply.
i apologize, my question was very poorly phrased.
si
hi. i am putting together a PKGBUILD. there are certain dependencies
required for cutting a release, rolling a version, etc. but, for just
downloading the sources and building, these dependencies are not needed.
can i leave dependencies *out* of makedepends that are only used for
non-mainline
hi. i am putting together a PKGBUILD. there are certain dependencies
required for cutting a release, rolling a version, etc. but, for just
downloading the sources and building, these dependencies are not needed.
can i leave dependencies *out* of makedepends that are only used for
non-mainline
> do properly.
> >
> > There is a GitHub repository (https://github.com/fancompute/ceviche) I
> want
> > to pack it up as a python library for ez maintenance if there is any
> future
> > update from the original authors.
> >
> > Last, I attach my PKG
Hi,
On Sunday, 19 June 2022 03:47:44 CEST Dunzhi Zhou via aur-general wrote:
> I am new to this mail list, hence please let me know anything if I didn't
> do properly.
Maybe you can also replace the direct calls to setup.py in build() and
package() with the PEP 517 workflow.
https://wiki.archli
ch my PKGBUILD file here. Please let me know if I should paste
the script in the mail instead.
Welcome and thank you for the contribution!
Unless a package produces architecture-dependent binaries, the
architecture for Python packages is “any”. A quick overview of the
repository shows that the
re is any future
update from the original authors.
Last, I attach my PKGBUILD file here. Please let me know if I should paste
the script in the mail instead.
Thanks
Here are a couple issues I've found at a first glance:
1) Your package is a VCS package that always builds the latest commi
ttach my PKGBUILD file here. Please let me know if I should paste
the script in the mail instead.
Thanks
PKGBUILD
Description: Binary data
I've pushed GCC 10 to the AUR:
https://aur.archlinux.org/packages/gcc10
It's based on the older GCC 9 PKGBUILD [1] with some elements from the
GCC 11 PKGBUILD [2].
It builds, installs, and seemingly runs OK, but it's something with
potential for hidden gotchas so if someone c
Hi again,
Am Dienstag, 14. Dezember 2021, 00:07:46 CET schrieb Jan Kohnert via aur-
general:
> So I thought about somehow let the user decide whether to run those
> expensive extra tests at build. Unfortunately I could not find a
> recommended way of doing so.
>
> Would it be an option to check a
b
On 2021-12-14 02:07, Jan Kohnert via aur-general wrote:
Hi,
I'm maintaining the eccodes aur package and would like to enable some
extra
tests in PKGBUILD. This can be done by downloading extra testdata and
put that
into the main build dir. As good as this may seem, it significantly
bl
On 2021-12-14 06:45, George Rawlinson via aur-general wrote:
On 21-12-14 00:07, Jan Kohnert via aur-general wrote:
Hi,
I'm maintaining the eccodes aur package and would like to enable some extra
tests in PKGBUILD. This can be done by downloading extra testdata and put that
into the main
On 21-12-14 00:07, Jan Kohnert via aur-general wrote:
> Hi,
>
> I'm maintaining the eccodes aur package and would like to enable some extra
> tests in PKGBUILD. This can be done by downloading extra testdata and put that
> into the main build dir. As good as this may seem, it
://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-pf#n151
https://aur.archlinux.org/cgit/aur.git/tree/build_pkgs?h=linux-pf#n9
rpmbuild has some --with and --without options to do stuff like you suggest
maybe something like this would be useful too.
Br,
Björn
Hi,
I'm maintaining the eccodes aur package and would like to enable some extra
tests in PKGBUILD. This can be done by downloading extra testdata and put that
into the main build dir. As good as this may seem, it significantly blows up
the
build time of the package.
So I thought
:08PM +, Vince via aur-general wrote:
> Hi again,
> It looks I didn't attach the correct files. I'm not sure what happened.
> Regardless, I have attached the files, and uploaded them to ix.io to
> be safe. Apologies for the confusion.
>
> PKGBUILD: http://ix.io/3uJY
>
Hi again,
It looks I didn't attach the correct files. I'm not sure what happened.
Regardless, I have attached the files, and uploaded them to ix.io to
be safe. Apologies for the confusion.
PKGBUILD: http://ix.io/3uJY
launcher.desktop: http://ix.io/3uzB
launcher.sh: http://ix.io/3uJZ
Hello aur-general,
Thank you for your help in the previous threads. I'm immensely grateful
for the feedback I got, and hope that I'm not polluting too much.
I have completed a PKGBUILD for REXPaint. I would be grateful if
someone could take a look and make sure that it ticks all the
nd
ask for some advice. There's generally always people around willing to
critique potential packages.
> I plan to submit a binary PKGBUILD for REXPaint, and since it's
> distributed as a portable binary for WINE, I have a couple questions
> about the guidelines:
>
> 1. Is
Hi guys,
same here, in my case it's Racer [1]. The start script is included as
source (I didn't supply a desktop file because I didn't find a suitable
icon). Also glad about constructive feedback!
All the best,
Michael
[1] https://aur.archlinux.org/packages/racer-cg/
Am Fr., 30. Juli 2021 um 17
wrote:
> Hello,
>
> This is my first time interacting with a mailing list, so please let me
> know if I've done something wrong, or I'm asking in the wrong place.
>
> I plan to submit a binary PKGBUILD for REXPaint, and since it's
> distributed as a portable binary f
Hi Vince,
About number 2, you can include the files alongside the PKGBUILD in the git
repo you push to the AUR, then add them to your "sources" array. Then, in
package(), you can use the "install" or "cp" command to move the files to their
desired location i
Hello,
This is my first time interacting with a mailing list, so please let me
know if I've done something wrong, or I'm asking in the wrong place.
I plan to submit a binary PKGBUILD for REXPaint, and since it's
distributed as a portable binary for WINE, I have a couple ques
On Tuesday, July 13, 2021 2:13:17 PM CST 悲剧小白 via aur-general wrote:
>I changed these two lines to "chmod -R go+rX $pkgdir/usr/share/icons"
The "quote" Eli mentioned means adding quotation marks around $pkgdir,
to avoid issues with whitespaces in the path.
--
Regards,
Felix Yan
signature.asc
D
thanks for your suggestion
> If this is just about lib files, you only need to set LD_LIBRARY_PATH,
> not some... stuff used to invoke a EULA???
I think it has nothing to do with EULA. The main interface of the game has a
link related to EULA, but this is a link to the official website.
I tr
On 7/13/21 12:38 AM, 悲剧小白 via aur-general wrote:
> 1.The AppRun file specifies the location of some lib files of the
> software. These variables seem to be called when the software is
> running.
If this is just about lib files, you only need to set LD_LIBRARY_PATH,
not some... stuff used to invok
1.The AppRun file specifies the location of some lib files of the software.
These variables seem to be called when the software is running.
2.The purpose of "chmod -R 755" is to change the permissions of these folders,
but it also affects the pictures in the final directory, so use "chmod 644"
On 7/12/21 11:50 PM, 悲剧小白 via aur-general wrote:
> I made a PKGBUILD for the "Badlion Client" software, but there will
> be some warnings during the build. How can I deal with this problem?
> If PKGBUILD has any other questions, please let me know.
>
> tips: Badlio
I made a PKGBUILD for the "Badlion Client" software, but there will be some
warnings during the build. How can I deal with this problem? If PKGBUILD has
any other questions, please let me know.
tips: Badlion Client is a third-party launcher for Minecraft games. To run the
game, y
Em maio 12, 2021 17:44 Jonathon Fernyhough via aur-general escreveu:
On 12/05/2021 18:30, Giancarlo Razzolini via aur-general wrote:
Em maio 12, 2021 14:11 alad via aur-general escreveu:
Going over the linked packages, they all fall in the latter category.
Terminate them with extreme prejud
Le mer. 12 mai 2021 à 23:24, alad via aur-general <
aur-general@lists.archlinux.org> a écrit :
> On 12/05/2021 22:52, Eli Schwartz via aur-general wrote:
> > On 5/12/21 4:47 PM, alad via aur-general wrote:
> >> On 12/05/2021 22:32, Pedro Henrique Lara Campos via aur-general wrote:
> - mhwd, a
On 13/05/2021 08:24, Frederik “Freso” S. Olesen via aur-general wrote:
On Wed, May 12, 2021 at 11:24:20PM +0200, alad via aur-general wrote:
On 12/05/2021 22:52, Eli Schwartz via aur-general wrote:
I followed the upstream URL to:
https://gitlab.com/garuda-linux/applications/mhwd-garuda
The on
On Wed, May 12, 2021 at 11:24:20PM +0200, alad via aur-general wrote:
> On 12/05/2021 22:52, Eli Schwartz via aur-general wrote:
> > I followed the upstream URL to:
> >
> > https://gitlab.com/garuda-linux/applications/mhwd-garuda
> >
> > The one-line README.md simply says:
> >
> > "mhwd for Garu
I am not sure what the rules are for licenses in the AUR.
But last time I checked most applications made by Garuda don't come with a
license.
Anyhow, as far as I know these packages weren't uploaded by maintainers of
Garuda. I think Garuda Linux is using its own repository for their custom
softwa
1 - 100 of 116 matches
Mail list logo
