Sorry, didn't see this was fixed.
Never mind.
Cheers
On viernes, 24 de enero de 2025 2:28:13 p. m. hora de Venezuela Klaus Tachtler
wrote:
> Hi,
>
> you're right - I've change to:
>
> ./configure --prefix=/usr --mandir=/usr/share/man
>
> Now it works!
>
> Klaus.
>
> On 1/24/25 19:21, Dou
Hi,
If I am not entirely wrong, the reason is because the directory most likely
already exists. So maybe try to move the contents into the directory
On viernes, 24 de enero de 2025 2:11:50 p. m. hora de Venezuela Klaus Tachtler
wrote:
> Hi,
>
> I am encountering a problem with the installatio
Hi,
you're right - I've change to:
./configure --prefix=/usr --mandir=/usr/share/man
Now it works!
Klaus.
On 1/24/25 19:21, Doug Newgard wrote:
On 1/24/25 12:11 PM, Klaus Tachtler wrote:
Hi,
I am encountering a problem with the installation of an AUR package I
have built.
During the i
On 1/24/25 12:11 PM, Klaus Tachtler wrote:
Hi,
I am encountering a problem with the installation of an AUR package I
have built.
During the installation I get the following error message:
error: failed to commit transaction (conflicting files)
libtlsrpt-git: /usr/local/share/man exists in f
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 only (
Le 03/07/2023 à 22:20, james smith a écrit :
one last question before adding it to the aur 1) can I have multiple
emails for the maintainer so that I have a backup incase one email
goes down 2) if the package goes to the main repos will I be the
maintainer or will the person who brought it to t
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 socket file in my home dir
Le 03/07/2023 à 07:00, james smith a écrit :
Now after making those changes running it, it doesn't correctly git
clone Neither source directory 'source' nor build directory 'build'
contain a build file meson.build. and I believe this command is the
culprit |printf "%s.r%s.%s" "$(git describe --
/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 send
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 continue this dis
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
Hi,
Here's how I would have wrote it (see commented changes at the bottom):
# Maintainer: Minecraftchest1
pkgname=file-sharing-tool
pkgver=0.2.0
pkgrel=1
pkgdesc="A tool to help setup file sharing using ssh."
arch=('any')
url=
["https://gitlab.com/minecraftchest1/steamdeck-file-share-tool";](ht
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=0
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_
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 makedep
Hello,
A package should only build one version of the codebase, so there is a
few tags you can use:
on its own normally means the latest STABLE version
-beta or -unstable etc can be made for
unstable builds, such as prerelease builds.
-git is used to build the latest commit in the master
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.)
cheers
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.
simpler: in
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
23 matches
Mail list logo
