Package Details: dragon-drag-and-drop 1.1.1-1

Git Clone URL: https://aur.archlinux.org/dragon-drag-and-drop.git (read-only, click to copy)
Package Base: dragon-drag-and-drop
Description: Simple drag-and-drop source/sink for X
Upstream URL: https://github.com/mwh/dragon
Licenses: GPL3
Submitter: Rhinoceros
Maintainer: Rhinoceros
Last Packager: Rhinoceros
Votes: 4
Popularity: 0.143444
First Submitted: 2019-07-25 06:47
Last Updated: 2020-03-01 07:11

Latest Comments

nourthe commented on 2020-11-16 11:39

@crdx Hi, that makes sense. Thanks for your explanation :D

crdx commented on 2020-11-15 15:19

@nourthe

Thank you for your contribution!

There is an implicit dependency on base-devel for all AUR packages, so it's normal that you had to install it.

See: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

Note: Packages in the AUR assume that the base-devel group is installed, i.e. they do not list the group's members as build dependencies explicitly.

nourthe commented on 2020-11-15 14:27

Hi. I'm relatively new in Arch (and Linux [and English lang :P]) this is my first contribution to the linux community :D.

I had tryed to install the package and it failed because it didn't find gtk header, or something like that.

I fixed it installing base-devel so there is an obvius dependency lefting in the dependency list that maybe you want to add. Here is a list of the packages that pacman installed (no re-install) from the base-devel group.

[ALPM] installed m4 (1.4.18-3)

[ALPM] installed autoconf (2.69-7)

[ALPM] installed automake (1.16.2-3)

[ALPM] installed bison (3.7.2-1)

[ALPM] installed flex (2.6.4-3)

[ALPM] installed pkgconf (1.7.3-1)

I would have liked to know which package solved my problem to help better. But I hope my contribution will serve you.

Regards, Nahuel

Rhinoceros commented on 2020-03-01 07:11

Thanks @Ordoviz for the reply and the reference. That makes perfect sense. Package updated.

Ordoviz commented on 2020-03-01 06:47

@Rhinoceros From PKGBUILD#source: Warning: The downloaded source filename must be unique because the SRCDEST directory can be the same for all packages. For instance, using the version number of the project as a filename potentially conflicts with other projects with the same version number.

Rhinoceros commented on 2020-03-01 03:06

@Ordoviz Thanks for the comment. Good point with removing git. What's the rationale behind having a unique name for the download? (I always assume users are making the package in a new directory.)

Ordoviz commented on 2020-02-29 21:46

A few improvements:

Remove the git make dependency. This is not a VCS package.

Use a unique name for the downloaded archive: "$pkgname-$pkgver::https://github.com/mwh/dragon/archive/v${pkgver}.tar.gz"

0xACE commented on 2019-10-12 19:05

@Rhinoceros. Okay, thank you.

Rhinoceros commented on 2019-10-11 22:57

@0xACE Yes, to avoid conflict with dragon from the Extra repository.

https://www.archlinux.org/packages/extra/x86_64/dragon/

0xACE commented on 2019-10-11 22:51

Any reason as to why dragon is being renamed to dragon-drag-and-drop ?