* Hector Martinez-Seara hse...@gmail.com [2014-06-05 08:56:00 +0300]:
Notice that before AUR 3 just calling makepkg --source was enough. Any
good reason
for this change? If there any possibility as Philip proposes that this is
done in the serve side?
I believe (though not 100% sure) this is
On Thu, 05 Jun 2014 at 08:12:23, Florian Bruhin wrote:
* Hector Martinez-Seara hse...@gmail.com [2014-06-05 08:56:00 +0300]:
Notice that before AUR 3 just calling makepkg --source was enough. Any
good reason
for this change? If there any possibility as Philip proposes that this is
done in
* Lukas Fleischer archli...@cryptocrack.de [2014-06-05 09:03:29 +0200]:
Note that this issue will vanish soon anyway since the next major AUR
release will provide Git repositories for all AUR packages. You will no
longer need to create source tarballs.
That sounds intresting! Is there some
On Thu, 05 Jun 2014 at 09:08:48, Florian Bruhin wrote:
* Lukas Fleischer archli...@cryptocrack.de [2014-06-05 09:03:29 +0200]:
Note that this issue will vanish soon anyway since the next major AUR
release will provide Git repositories for all AUR packages. You will no
longer need to create
On Thu, Jun 05, 2014 at 09:28:15AM +0200, Lukas Fleischer wrote:
On Thu, 05 Jun 2014 at 09:08:48, Florian Bruhin wrote:
* Lukas Fleischer archli...@cryptocrack.de [2014-06-05 09:03:29 +0200]:
Note that this issue will vanish soon anyway since the next major AUR
release will provide Git
On Thu, 05 Jun 2014 at 09:52:11, William Giokas wrote:
On Thu, Jun 05, 2014 at 09:28:15AM +0200, Lukas Fleischer wrote:
On Thu, 05 Jun 2014 at 09:08:48, Florian Bruhin wrote:
* Lukas Fleischer archli...@cryptocrack.de [2014-06-05 09:03:29 +0200]:
Note that this issue will vanish soon
On 28 May 2014 04:42, Lukas Fleischer archli...@cryptocrack.de wrote:
Note that in order to build source packages for the AUR, you will now
need to use a tool called mkaurball (instead of `makepkg --source`). It
is included in the pkgbuild-introspection package [2].
Why do files/directories
Why do files/directories inside a src tarball need to be 644/755
respectively? [1]
I run with umask 027 so this error is going to bite me every time I
create a new PKGBUILD to upload, or forget to change the permissions
on my existing PKGBUILD's.
I have to agree with Philip. I also have
It would be useful for makepkg to be able to build ony one specific
package from a split package though, no? Eg. makepkg
--only=package1,package2
J. Leclanche
On Sun, Jun 1, 2014 at 9:57 PM, Johannes Löthberg johan...@kyriasis.com wrote:
On 01/06, Jerome Leclanche wrote:
.. bummer.
Is that
On Mon, Jun 2, 2014 at 7:54 AM, Jerome Leclanche adys...@gmail.com wrote:
It would be useful for makepkg to be able to build ony one specific
package from a split package though, no? Eg. makepkg
--only=package1,package2
J. Leclanche
I guess one problem for this is that some of the
On Mon, Jun 2, 2014 at 7:54 AM, Jerome Leclanche adys...@gmail.com wrote:
It would be useful for makepkg to be able to build ony one specific
package from a split package though, no? Eg. makepkg
--only=package1,package2
J. Leclanche
makepkg can already do that:
--pkg list
On Mon, Jun 2, 2014 at 10:18 AM, Eric Bélanger snowmanisc...@gmail.com wrote:
On Mon, Jun 2, 2014 at 7:54 AM, Jerome Leclanche adys...@gmail.com wrote:
It would be useful for makepkg to be able to build ony one specific
package from a split package though, no? Eg. makepkg
Hi
I'm trying to upload a split package of sddm -qt5-git and -git
(attached), but when I upload it, it says: You are not allowed to
overwrite the sddm-qt5-git package.. I'm a maintainer of both of
course.
Is this a bug? If not, what's the correct course of action?
J. Leclanche
On Fri, May 30,
Hi,
On Sun, 01 Jun 2014 at 13:36:29, Jerome Leclanche wrote:
Hi
I'm trying to upload a split package of sddm -qt5-git and -git
(attached), but when I upload it, it says: You are not allowed to
overwrite the sddm-qt5-git package.. I'm a maintainer of both of
course.
Is this a bug? If not,
That's very unfortunate and quite a bit counter-intuitive. Is this final?
J. Leclanche
On Sun, Jun 1, 2014 at 2:26 PM, Lukas Fleischer
archli...@cryptocrack.de wrote:
Hi,
On Sun, 01 Jun 2014 at 13:36:29, Jerome Leclanche wrote:
Hi
I'm trying to upload a split package of sddm -qt5-git and
On Sun, 01 Jun 2014 at 16:16:08, Jerome Leclanche wrote:
That's very unfortunate and quite a bit counter-intuitive. Is this final?
[...]
No, it's not. As I said in the other thread [1] on this topic, I am open
for suggestions.
[1]
On 2014-06-01 06:36, Jerome Leclanche wrote:
Hi
I'm trying to upload a split package of sddm -qt5-git and -git
(attached), but when I upload it, it says: You are not allowed to
overwrite the sddm-qt5-git package.. I'm a maintainer of both of
course.
Is this a bug? If not, what's the correct
On 01/06, Doug Newgard wrote:
Please don't. You'll force the user to have both qt4 and qt5 installed
even if they just want one of them.
No?.. Both will be built by default, but building and installing
packages are two very separate things, and split packages exist for the
sole purpose of
On 2014-06-01 09:50, Johannes Löthberg wrote:
On 01/06, Doug Newgard wrote:
Please don't. You'll force the user to have both qt4 and qt5 installed
even if they just want one of them.
No?.. Both will be built by default, but building and installing
packages are two very separate things ...
You'll need qt4 and qt5 installed to build the package though.
So that means a large download of qt5, unnecessary writes to the users
SSD, increased install time, and then having to remove qt5 again
afterwards! (or the opposite way around qt5-qt4)
On 1 June 2014 15:51, Doug Newgard
On 01/06, Steven Honeyman wrote:
You'll need qt4 and qt5 installed to build the package though.
If they don't want that they can just modify the PKGBUILD ever so
slightly instead of the maintainer to have to maintain several versions
of the same PKGBUILD
--
Sincerely,
Johannes Löthberg
On 01/06, Doug Newgard wrote:
No?.. Both will be built by default, but building and installing
packages are two very separate things ...
In a binary repo, that is true, but not in the AUR.
Yes it is, makepkg just builds packages by default unless you
explicitly tell it to install them too.
On 2014-06-01 10:02, Johannes Löthberg wrote:
On 01/06, Steven Honeyman wrote:
You'll need qt4 and qt5 installed to build the package though.
If they don't want that they can just modify the PKGBUILD ever so
slightly instead of the maintainer to have to maintain several
versions of the same
On 2014-06-01 10:03, Johannes Löthberg wrote:
On 01/06, Doug Newgard wrote:
No?.. Both will be built by default, but building and installing
packages are two very separate things ...
In a binary repo, that is true, but not in the AUR.
Yes it is, makepkg just builds packages by default
On 01/06, Doug Newgard wrote:
In the AUR, you specifically build packages to install them. When
building for binary repos, you build them to upload them for others to
install them. HUGE difference.
The AUR is a repository for hosting PKGBUILDs for packages not in the
repos. Do not conflate
On 2014-06-01 10:09, Johannes Löthberg wrote:
On 01/06, Doug Newgard wrote:
In the AUR, you specifically build packages to install them. When
building for binary repos, you build them to upload them for others to
install them. HUGE difference.
The AUR is a repository for hosting PKGBUILDs
On Sun, Jun 01, 2014 at 10:10:35AM -0500, Doug Newgard wrote:
On 2014-06-01 10:09, Johannes Löthberg wrote:
On 01/06, Doug Newgard wrote:
In the AUR, you specifically build packages to install them. When
building for binary repos, you build them to upload them for others to
install them. HUGE
On 2014-06-01 10:15, Dave Reisner wrote:
On Sun, Jun 01, 2014 at 10:10:35AM -0500, Doug Newgard wrote:
On 2014-06-01 10:09, Johannes Löthberg wrote:
On 01/06, Doug Newgard wrote:
In the AUR, you specifically build packages to install them. When
building for binary repos, you build them to
On Sun, Jun 01, 2014 at 10:20:32AM -0500, Doug Newgard wrote:
On 2014-06-01 10:15, Dave Reisner wrote:
On Sun, Jun 01, 2014 at 10:10:35AM -0500, Doug Newgard wrote:
On 2014-06-01 10:09, Johannes Löthberg wrote:
On 01/06, Doug Newgard wrote:
In the AUR, you specifically build packages to
I don't really understand why AUR helpers can't be updated to only
build the package you want in the split pkgbuild. If you look at my
source package, the makedepends are only in their respective package.
Is makepkg limited in that way? Because if it is, this is a good
feature to have.
J.
On 2014-06-01 10:56, Jerome Leclanche wrote:
I don't really understand why AUR helpers can't be updated to only
build the package you want in the split pkgbuild. If you look at my
source package, the makedepends are only in their respective package.
Is makepkg limited in that way? Because if it
.. bummer.
Is that final as well?
J. Leclanche
On Sun, Jun 1, 2014 at 5:03 PM, Doug Newgard scim...@archlinux.info wrote:
On 2014-06-01 10:56, Jerome Leclanche wrote:
I don't really understand why AUR helpers can't be updated to only
build the package you want in the split pkgbuild. If you
On 01/06, Jerome Leclanche wrote:
.. bummer.
Is that final as well?
J. Leclanche
Anything else would be pointless either way. makedepends are used when
building, not when packaging something, so in that case you'd rather
want split packages to be able to have a split build function.
--
On Fri, 30 May 2014 at 03:54:09, Hong Shick Pak wrote:
[...]
I didn't try changing my AUR username before the update, but I'm trying
to it from Hspasta to Hspak and I seem to be getting an irrelevant
(generic?) error messages:
The username is invalid.
It must be between 3 and 16
On Thu, 29 May 2014 at 10:52:58, Andreas Radke wrote:
[...]
The RSS feed seems empty.
Fixed in maint. Thanks!
-Andy
On Tue, May 27, 2014, at 11:42 AM, Lukas Fleischer wrote:
Hello,
I am pleased to announce that AUR 3.0.0 has just been released. The
official AUR setup [1] has already been updated.
Note that in order to build source packages for the AUR, you will now
need to use a tool called mkaurball
Hello,
I am pleased to announce that AUR 3.0.0 has just been released. The
official AUR setup [1] has already been updated.
Note that in order to build source packages for the AUR, you will now
need to use a tool called mkaurball (instead of `makepkg --source`). It
is included in the
37 matches
Mail list logo
