Depends on the project, but upstream usually has a list of dependencies in
the build instructions or somewhere at the development page.
What package are you trying to make a PKGBUILD for specifically?
tors 22 feb. 2018 kl. 02:06 skrev Future Trailer via aur-general <
aur-general@archlinux.org>:
Thank you for the reply. And forgive me for being a newbie. I am just
confuse how do you get the upstream lists?
On Sun, Feb 18, 2018 at 11:11 PM, Robin Broda via aur-general <
aur-general@archlinux.org> wrote:
> Try to figure out what upstream lists as dependencies, & check against
> namcap[1]
Yeah, forgot about that too... I guess one of those days. Fixed now. Thanks
for the help.
Regards,
Konstantin
On Wed, Feb 21, 2018 at 2:43 PM, Ankit R Gadiya wrote:
> Hey,
>
> But anybody using the package is pulling the git repository and so it
> automatically uses the master
On 21 February 2018 at 13:37, Konstantin Gizdov wrote:
> Hi Morgan,
>
> Indeed on the surface it looks that way. The dev does not explicitly make
> releases anymore for some reason, but I work with him and I know which
> commits are actually supposed to be releases and only choose
Hey,
But anybody using the package is pulling the git repository and so it
automatically uses the master HEAD, and I don't see any command in
prepare() for choosing the commits.
On 02/21/2018 07:07 PM, Konstantin Gizdov wrote:
Hi Morgan,
Indeed on the surface it looks that way. The dev
Hi Morgan,
Indeed on the surface it looks that way. The dev does not explicitly make
releases anymore for some reason, but I work with him and I know which
commits are actually supposed to be releases and only choose those.
Regards,
Konstantin
On Wed, Feb 21, 2018 at 2:19 PM, Morgan Adamiec via
Hi Michael,
You are looking probably at the incorrect version of the package on AUR.
But anyway, that was not the issue. I forgot to `cd` in to the correct
folder.
Regards,
Konstantin
On Wed, Feb 21, 2018 at 2:18 PM, Michael Kogan
wrote:
> I think, Konstantin refers to
Hi Bruno,
Yeah, my bad. Forgot to add `cd "${srcdir}/${pkgname}/build"` in the
`pacakge()` directive. It all works now.
Regards,
Konstantin
On Wed, Feb 21, 2018 at 2:14 PM, Bruno Pagani via aur-general <
aur-general@archlinux.org> wrote:
> Le 21/02/2018 à 13:55, Konstantin Gizdov a écrit :
>
>
On 21 February 2018 at 13:14, Bruno Pagani via aur-general
wrote:
> Le 21/02/2018 à 13:55, Konstantin Gizdov a écrit :
>
>> Hi,
>>
>> I'm having trouble making a package under the Arch Packaging Standards. The
>> package in question is `simpletools`.
>>
>> The problem
I think, Konstantin refers to
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=simpletools
Konstantin, I think, you are missing the make command (at least I only see
cmake and make install commands. It should look something like
build() {
mkdir -p "${srcdir}/${pkgname}/build"
cd
Le 21/02/2018 à 13:55, Konstantin Gizdov a écrit :
> Hi,
>
> I'm having trouble making a package under the Arch Packaging Standards. The
> package in question is `simpletools`.
>
> The problem I'm having is that if I use `prepare()` & `build()` directives
> as intended, then the target `make
Hi,
I'm having trouble making a package under the Arch Packaging Standards. The
package in question is `simpletools`.
The problem I'm having is that if I use `prepare()` & `build()` directives
as intended, then the target `make install` does not exist when called from
inside `package()`
On 02/12/2018 03:30 PM, Brad Fanella via aur-general wrote:
> On 02/12/2018 06:52 AM, Eli Schwartz via aur-general wrote:
>> Brad, please create a new AUR account, as you will need one to interact
>> with the AUR for various TU duties if you are re-elected. (This is
>> independent of whether you
13 matches
Mail list logo