Re: [aur-general] maynard-git package review request

[Alive 4ever]

On Sun, Aug 21, 2016 at 11:15:16PM -0400, Eli Schwartz via aur-general wrote:
> To quote the Wiki[1]...
> 
> Both methods can also be combined, to support repositories that start
> without a tag but get tagged later on (uses a bashism):
> 
> ```
> pkgver() {
>   cd "$pkgname"
>   ( set -o pipefail
> git describe --long 2>/dev/null | sed 's/\([^-]*-g\)/r\1/;s/-/./g' ||
> printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse
> --short HEAD)"
>   )
> }
> ```
For now, I'll stick to use no-tag version. Tagged version will be
considered when the time comes.
> 
> > I think configure flag --libexecdir is needed to put maynard executable
> > under /usr/lib/maynard. Without libexecdir, the resulting executable is
> > placed under /usr/libexec/maynard and it's kind of messy.
> > 
> > I should have tested the PKGBUILD under clean chroot to specify exact
> > dependencies.
> > 
> > Thanks for your feedback.
> > 
> 
> Hmm, maybe -- I haven't tried it, so I wouldn't know. But libexecdir
> does ring a bell...
> What about bindir, libdir, and sysconfdir though? IIRC those should
> already have the right default values.

Removing bindir, libdir, and sysconfdir flags creates no problems so
far. It put the binaries and libraries in the right place according to
Arch Linux packaging standards.

> 
> -- 
> Eli Schwartz
> 
> 
> [1] https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

Re: [aur-general] maynard-git package review request

[Alive 4ever]

On Sun, Aug 21, 2016 at 10:16:44AM -0400, Eli Schwartz via aur-general wrote:
> On 08/21/2016 06:39 AM, Alive 4ever wrote:
> > Feel free to test this package. Remember to  submit bug reports and
> > feedback upstream. Patches and suggestions for improving PKGBUILD are
> > welcome.
> 
> Why so many comments?
> 
> Other than that, it looks fine except for your usage of ${pkgname%-VCS}
> instead of ${pkgname%-git} -- did you forget to customize that?
> 
> I would also include an empty line in between the Maintainer line and
> the body of the PKGBUILD, for readability. Additionally, you can again
> use ${pkgname%-git} in the url, to highlight the connection between the
> upstream url and the package name, and use ${url} in the sources array.
> 
> Also note that git will by default clone the repo into the last url
> component with the ".git" part trimmed off, so no need to manually
> specify it.
> 
> ...
> 
> How many of those configure flags are necessary? Most projects only need
> the --prefix to be specified...

I intentinally put the comments from PGBUILD-vcs.proto, thinking that
someday there will be git tag. Currently, there is no tag available.
`git describe` shows no output. I should clean this mess up.

About leftover ${pkgname%-VCS}, I just forgot to change it to git.

I think configure flag --libexecdir is needed to put maynard executable
under /usr/lib/maynard. Without libexecdir, the resulting executable is
placed under /usr/libexec/maynard and it's kind of messy.

I should have tested the PKGBUILD under clean chroot to specify exact
dependencies.

Thanks for your feedback.

[aur-general] maynard-git package review request

[Alive 4ever]

Hi aur!

I am creating a new PKGBUILD[1] for maynard[2]. It's a new desktop shell
for use with wayland display protocol.

It's not a complete desktop environment. It's just a shell for use with
weston compositor.

The resulting pkg.tar.xz file is just 32KB.

Maynard crashes frequently, so I wouldn't recommend it for use with
important files. Some actions that triggered the crash:

1. Dragging any application window.
2. Interaction with Libreoffice menu using mouse pointer.
3. Another random mouse action.

Feel free to test this package. Remember to  submit bug reports and
feedback upstream. Patches and suggestions for improving PKGBUILD are
welcome.


[1] https://aur.archlinux.org/packages/maynard-git/
[2] https://github.com/raspberrypi/maynard

[aur-general] mailman command

[Alive 4ever]

On Tue, Aug 16, 2016 at 03:20:48PM +0900, Dragon ryu via aur-general wrote:
> password
You should send your message to aur-general-request instead of
aur-general.

Re: [aur-general] Password reset

[Alive 4ever]

On Sat, Aug 13, 2016 at 01:01:04AM +0200, Dwarf O wrote:
> Hi there,
> 
> I have tried to reset my password using the online form but have not
> received an email. It's been more than a day now and was wondering if
> someone could reset it manually. Thanks!
You can send a mail containing 'password' in the message body to
'aur-general-request'. You should get your password in the reply.

Re: [aur-general] [PATCH] core/links:Bump to version 2.13

[Alive 4ever]

On Fri, Aug 05, 2016 at 01:45:18AM +0800, Chi Hsuan Yen via aur-general wrote:
> Maybe the only way is waiting. I have once submitted patches of PKGBUILDs
> to bugs.archlinux.org, but I don't think a trivial version bump will be
> accepted as a valid bug, as the bug tracker says: "Do NOT report bugs for
> outdated packages!"
> 
> On Thu, Aug 4, 2016 at 12:41 AM, Alive 4ever <alive4e...@live.com> wrote:
> 
> > Since links package has been flagged out of date for almost one month, I
> > can't help myself to contribute a patch and stop bugging maintainer to
> > package an updated version.
> >
> > I hope this is the right place to submit the patch.
> >
> > --
> > Upgrade links to version 2.13
> >
> > Signed-off-by: Alif <alive4e...@live.com>
> > ---
> >  trunk/PKGBUILD | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
> > index 85ce55c..3f2a3bf 100644
> > --- a/trunk/PKGBUILD
> > +++ b/trunk/PKGBUILD
> > @@ -2,8 +2,8 @@
> >  # Maintainer: Eric Bélanger <e...@archlinux.org>
> >
> >  pkgname=links
> > -pkgver=2.12
> > -pkgrel=2
> > +pkgver=2.13
> > +pkgrel=1
> >  pkgdesc="A text WWW browser, similar to Lynx"
> >  arch=('i686' 'x86_64')
> >  url="http://links.twibright.com/;
> > @@ -15,7 +15,7 @@ optdepends=('libx11: for using xlinks'
> > 'libpng: for using xlinks'
> > 'librsvg: for using xlinks')
> >  source=(http://links.twibright.com/download/${pkgname}-${pkgver}.tar.bz2
> > links.desktop)
> > -sha1sums=('952dfecded9496ff1a73184ce538d08dbbb5152b'
> > +sha1sums=('ee5ef004723664d3928e29a603cb150db013603f'
> >'f600e27c2a7118f7dd07a10230aa44463a02')
> >
> >  prepare() {
> > --
> > 2.9.2
> >

It's right. Development isn't just fixing bugs. Development also
involves making improvements.

The Arch Linux Flyspray bugtracker is just about one side of Arch Linux
development: fixing bugs.

Making improvement should be discussed in a development mailing list and
I think this is the only place suitable for discussing Arch Linux
development, mostly regarding improvements.

* For the newly elected TU, can you help with packaging new 'links'
* package, so that it's available from the repository, at least make a
* staging to test repository.

[aur-general] [PATCH] core/links:Bump to version 2.13

[Alive 4ever]

Since links package has been flagged out of date for almost one month, I
can't help myself to contribute a patch and stop bugging maintainer to
package an updated version.

I hope this is the right place to submit the patch.

--
Upgrade links to version 2.13

Signed-off-by: Alif 
---
 trunk/PKGBUILD | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index 85ce55c..3f2a3bf 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -2,8 +2,8 @@
 # Maintainer: Eric Bélanger 
 
 pkgname=links
-pkgver=2.12
-pkgrel=2
+pkgver=2.13
+pkgrel=1
 pkgdesc="A text WWW browser, similar to Lynx"
 arch=('i686' 'x86_64')
 url="http://links.twibright.com/;
@@ -15,7 +15,7 @@ optdepends=('libx11: for using xlinks'
'libpng: for using xlinks'
'librsvg: for using xlinks')
 source=(http://links.twibright.com/download/${pkgname}-${pkgver}.tar.bz2 
links.desktop)
-sha1sums=('952dfecded9496ff1a73184ce538d08dbbb5152b'
+sha1sums=('ee5ef004723664d3928e29a603cb150db013603f'
   'f600e27c2a7118f7dd07a10230aa44463a02')
 
 prepare() {
-- 
2.9.2