FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 11-18-2010, 07:30 AM
Kaiting Chen
 
Default ?

Can AUR helpers go into [community]? `burp` and `cower` each have over ten
votes and qualify, but I never see AUR helpers in binary form so I thought I
would ask. --Kaiting.

--
Kiwis and Limes: http://kaitocracy.blogspot.com/
 
Old 11-18-2010, 07:54 AM
Isaac Dupree
 
Default ?

On 11/18/10 03:30, Kaiting Chen wrote:

Can AUR helpers go into [community]? `burp` and `cower` each have over ten
votes and qualify, but I never see AUR helpers in binary form so I thought I
would ask. --Kaiting.


No.

I looked to see where this was documented on the wiki and the closest I
found in a couple minutes was

https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_Packages_from_the_ AUR
"Note: There is not and will never be an official mechanism for
installing build material from UNSUPPORTED. All users should be familiar
with the build process."
...being in [community] makes it too official (although this reasoning
is not trivially obvious from the quote). It makes it possible to
install the AUR Helper without ever having that moment of
experience/familiarity using makepkg (to draw from the quote's second
sentence).


-Isaac
 
Old 11-18-2010, 10:00 AM
Pierre Schmitz
 
Default ?

On Thu, 18 Nov 2010 08:24:33 +0100, Andrea Scarpino
<andrea@archlinux.org> wrote:
> On Thursday 18 November 2010 07:20:54 Daniel Isenmann wrote:
>> That's right, I made such a rebuild script. But I'm not really sure if I
>> have it any longer. Have to check it at home. It was a hackish bash
>> script which increased the pkgrel variable and rebuild the package,
>> that's all.
> We have to use the package() function and to remove the ||return 1 stuff. I
> don't think that do this job with a script is a good idea.
>
> Anyway, count on me for this rebuild.

Dito, could help also. Btw: We put it into testing first anyway, so the
permission to move them to core is not really a blocker here.

Allan, how do we chosse packages? I could easily do a query like "show
me all packages which are older than xx" etc.. Just let me know.

--
Pierre Schmitz, https://users.archlinux.de/~pierre
 
Old 11-18-2010, 10:14 AM
Allan McRae
 
Default ?

On 18/11/10 21:00, Pierre Schmitz wrote:

On Thu, 18 Nov 2010 08:24:33 +0100, Andrea Scarpino
<andrea@archlinux.org> wrote:

On Thursday 18 November 2010 07:20:54 Daniel Isenmann wrote:

That's right, I made such a rebuild script. But I'm not really sure if I
have it any longer. Have to check it at home. It was a hackish bash
script which increased the pkgrel variable and rebuild the package,
that's all.

We have to use the package() function and to remove the ||return 1 stuff. I
don't think that do this job with a script is a good idea.

Anyway, count on me for this rebuild.


Dito, could help also. Btw: We put it into testing first anyway, so the
permission to move them to core is not really a blocker here.

Allan, how do we chosse packages? I could easily do a query like "show
me all packages which are older than xx" etc.. Just let me know.



I have a list that I will put somewhere with all packages that are not
.xz format (except those that need to stay .gz) and not in the package
pool directory sorted by date since last built. I will dump it to a
TODO list/wiki page at some stage.


Allan
 
Old 11-18-2010, 10:34 AM
Pierre Schmitz
 
Default ?

On Thu, 18 Nov 2010 21:14:20 +1000, Allan McRae <allan@archlinux.org>
wrote:
> On 18/11/10 21:00, Pierre Schmitz wrote:
>> On Thu, 18 Nov 2010 08:24:33 +0100, Andrea Scarpino
>> <andrea@archlinux.org> wrote:
>>> On Thursday 18 November 2010 07:20:54 Daniel Isenmann wrote:
>>>> That's right, I made such a rebuild script. But I'm not really sure if I
>>>> have it any longer. Have to check it at home. It was a hackish bash
>>>> script which increased the pkgrel variable and rebuild the package,
>>>> that's all.
>>> We have to use the package() function and to remove the ||return 1 stuff. I
>>> don't think that do this job with a script is a good idea.
>>>
>>> Anyway, count on me for this rebuild.
>>
>> Dito, could help also. Btw: We put it into testing first anyway, so the
>> permission to move them to core is not really a blocker here.
>>
>> Allan, how do we chosse packages? I could easily do a query like "show
>> me all packages which are older than xx" etc.. Just let me know.
>>
>
> I have a list that I will put somewhere with all packages that are
> not .xz format (except those that need to stay .gz) and not in the
> package pool directory sorted by date since last built. I will dump
> it to a TODO list/wiki page at some stage.
>
> Allan

I'd say just create a todo list and maybe create a check list about
what to do with those packages then. (e.g. package functions, removing
|| return 1 or look for an update in general.)

--
Pierre Schmitz, https://users.archlinux.de/~pierre
 
Old 11-18-2010, 01:43 PM
Ionuț Bîru
 
Default ?

On 11/18/2010 10:30 AM, Kaiting Chen wrote:

Can AUR helpers go into [community]? `burp` and `cower` each have over ten
votes and qualify, but I never see AUR helpers in binary form so I thought I
would ask. --Kaiting.



no. we can't support unsupported software :P

--
Ionuț
 
Old 11-18-2010, 06:00 PM
Stefan Husmann
 
Default ?

Am 18.11.2010 09:30, schrieb Kaiting Chen:
> Can AUR helpers go into [community]? `burp` and `cower` each have over ten
> votes and qualify, but I never see AUR helpers in binary form so I thought I
> would ask. --Kaiting.
>

I think if we should discuss this if the AUR helper does not hide the build
process itself from the user. Cower for instance is for just downloading the
taurball (you still have to run makepkg manually), and burp is for just
uploading it.

I would have nothing against having tools like this in [community]. But
everything beyond that should be strictly rejected.

Regards Stefan
 
Old 11-18-2010, 06:03 PM
Ionuț Bîru
 
Default ?

On 11/18/2010 09:00 PM, Stefan Husmann wrote:

Am 18.11.2010 09:30, schrieb Kaiting Chen:

Can AUR helpers go into [community]? `burp` and `cower` each have over ten
votes and qualify, but I never see AUR helpers in binary form so I thought I
would ask. --Kaiting.



I think if we should discuss this if the AUR helper does not hide the build
process itself from the user. Cower for instance is for just downloading the
taurball (you still have to run makepkg manually), and burp is for just
uploading it.


two tools for managing aur is not what we want.

maybe cower could get upload support too

--
Ionuț
 
Old 11-18-2010, 06:31 PM
Matthew Gyurgyik
 
Default ?

On 11/18/2010 02:03 PM, Ionuț Bîru wrote:

On 11/18/2010 09:00 PM, Stefan Husmann wrote:

Am 18.11.2010 09:30, schrieb Kaiting Chen:
Can AUR helpers go into [community]? `burp` and `cower` each have
over ten
votes and qualify, but I never see AUR helpers in binary form so I
thought I

would ask. --Kaiting.



I think if we should discuss this if the AUR helper does not hide the
build
process itself from the user. Cower for instance is for just
downloading the

taurball (you still have to run makepkg manually), and burp is for just
uploading it.


two tools for managing aur is not what we want.

maybe cower could get upload support too


Slurpy already does that...
*download, searches, and uploads
*created by rson
*maintained by our very own, MrElendig.
*No build support
*Written in Python!


https://github.com/rson/slurpy
 
Old 11-18-2010, 07:10 PM
Stefan Husmann
 
Default ?

Am 18.11.2010 20:31, schrieb Matthew Gyurgyik:
> On 11/18/2010 02:03 PM, Ionuț Bîru wrote:
>> On 11/18/2010 09:00 PM, Stefan Husmann wrote:
>>> Am 18.11.2010 09:30, schrieb Kaiting Chen:
>>>> Can AUR helpers go into [community]? `burp` and `cower` each have over ten
>>>> votes and qualify, but I never see AUR helpers in binary form so I thought I
>>>> would ask. --Kaiting.
>>>>
>>>
>>> I think if we should discuss this if the AUR helper does not hide the build
>>> process itself from the user. Cower for instance is for just downloading the
>>> taurball (you still have to run makepkg manually), and burp is for just
>>> uploading it.
>>
>> two tools for managing aur is not what we want.
>>
>> maybe cower could get upload support too
>>
I definitely prefer two tools for uploading and downloading. In fact I only use
burp for uploading, and not cower but aurdownload (in aurscripts) for downloading.

> Slurpy already does that...
> *download, searches, and uploads
I know slurpy, but I am not totally convinced. It does not fit to my workflow. I
have two directory-trees where my PKGBUILDs live, and slurpy is only aware of one
of them (the one you cd to).
> *created by rson
Who is this? Do I need to know him or her?
> *maintained by our very own, MrElendig.
Also cower and burp are made by an archer.
> *No build support
That is okay!
> *Written in Python!
>
That is a disadvantage over cower and burp, which are written in C.
>
> https://github.com/rson/slurpy
>
Never mind, it is not completely unusable.

But the problem is not which tool we want to have in [community] but to make
up a rule what kind of help such a helper might provide to be seen as candidate
for inclusion in [community]. I tried to propose an criterium in my previous post.

Regards Stefan
 

Thread Tools




All times are GMT. The time now is 05:36 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org