On Mon, 8 Oct 2018 13:43:28 +0700
Tom Hale wrote:
> On 8/10/18 1:35 pm, Doug Newgard via aur-general wrote:
> > namcap's output is informational, nothing more. Taking it as gospel or
> > using it
> > as any kind of automated checking instead of actually reading the output is
> > not
> > sane.
On 8/10/18 1:35 pm, Doug Newgard via aur-general wrote:
namcap's output is informational, nothing more. Taking it as gospel or using it
as any kind of automated checking instead of actually reading the output is not
sane.
For greater specificity, the informational output can be split into:
* I
On 10/8/18 2:23 AM, Tom Hale wrote:
> I noticed that even when namcap prints out errors, it still exits 0.
>
> I raised this at:
> https://bugs.archlinux.org/task/60333
>
> It was closed:
>
> Reason for closing: Not a bug
> Additional comments about closing: namcap runs fine, so exiting with an
On Mon, 8 Oct 2018 13:23:03 +0700
Tom Hale wrote:
> I noticed that even when namcap prints out errors, it still exits 0.
>
> I raised this at:
> https://bugs.archlinux.org/task/60333
>
> It was closed:
>
> Reason for closing: Not a bug
> Additional comments about closing: namcap runs fine, so
I noticed that even when namcap prints out errors, it still exits 0.
I raised this at:
https://bugs.archlinux.org/task/60333
It was closed:
Reason for closing: Not a bug
Additional comments about closing: namcap runs fine, so exiting with an
error makes no sense
To me the "reason for closing
On 10/7/18 10:45 PM, Tom Hale wrote:
> Thanks all for the great reviews.
>
> Thank you in particular to those who said WHY changes were suggested. I
> now feel empowered to go on to package rambox-os.
>
> I believe I have incorporated all the feedback I received in the below.
>
> If I missed som
Thanks all for the great reviews.
Thank you in particular to those who said WHY changes were suggested. I
now feel empowered to go on to package rambox-os.
I believe I have incorporated all the feedback I received in the below.
If I missed something it is by mistake - and I ask for your gener
On October 7, 2018 5:41:41 PM GMT+02:00, Brett Cornwall via aur-general
wrote:
>Hello, fellow Archers. My name is Brett and I've been making PKGBUILDs
>for the AUR for some time under the moniker 'Ainola'. A number of these
>
>packages have been kindly pulled into [community] by David Runge. I'v
On 10/7/18 11:41 AM, Brett Cornwall via aur-general wrote:
> Hello, fellow Archers. My name is Brett and I've been making PKGBUILDs
> for the AUR for some time under the moniker 'Ainola'. A number of these
> packages have been kindly pulled into [community] by David Runge. I've
> since had a desire
Hello, fellow Archers. My name is Brett and I've been making PKGBUILDs
for the AUR for some time under the moniker 'Ainola'. A number of these
packages have been kindly pulled into [community] by David Runge. I've
since had a desire to get some of my other packages into [community], so
I'm inte
On Sun, Oct 07, 2018 at 10:46:56AM -0400, Eli Schwartz via aur-general wrote:
> On 10/7/18 5:58 AM, Florian Bruhin wrote:
> > That seems like a good idea, but I'm not sure a PKGBUILD should set it.
> > Maybe makepkg even does it by itself?
> Who says it's a good idea? When is it a good idea? How do
On 10/7/18 5:32 AM, Tom Hale wrote:
> Here's a version which builds from HEAD of the default branch.
>
> Comments please.
Well, by convention you would post this inline instead of as an
attachment since it is easier to review that way...
> _pkgname=nixnote2
> _repo_url="https://github.com/robert
On 7/10/18 4:58 pm, Florian Bruhin wrote:
On Sun, Oct 07, 2018 at 04:32:04PM +0700, Tom Hale wrote:
Guess you could use $_pkgname here for nixnote2. Also not sure
specifying the version there is a good idea.
https://wiki.archlinux.org/index.php/PKGBUILD#provides says:
Note: The version that
On Sun, Oct 07, 2018 at 04:32:04PM +0700, Tom Hale wrote:
> Comments please.
Some random stuff I noticed:
> _repo_url="https://github.com/robert7/${_pkgname}.git";
Probably not needed when you only need it in source.
> provides=("nixnote=${pkgver%.r*}" "nixnote2=${pkgver%.r*}")
Guess you could
Here's a version which builds from HEAD of the default branch.
Comments please.
--
Tom Hale
# Maintainer: Tom Hale
# Contributor: twa022
_pkgname=nixnote2
_repo_url="https://github.com/robert7/${_pkgname}.git";
pkgname=${_pkgname}-git
pkgver=v2.1.0.beta3.r95.g8f235769
pkgrel=1
pkgdesc="Evern
15 matches
Mail list logo
