[aur-general] How to handle interchangeable dependencies?

[hollunder at gmx.at]

On Mon, 6 Apr 2009 10:27:21 -0400
Loui Chang <louipc.ist at gmail.com> wrote:

> On Mon, Apr 06, 2009 at 04:21:53PM +0200, hollunder at gmx.at wrote:
> > On Mon, 6 Apr 2009 10:02:41 -0400
> > Loui Chang <louipc.ist at gmail.com> wrote:
> > 
> > > On Mon, Apr 06, 2009 at 03:45:43PM +0200, hollunder at gmx.at wrote:
> > > > On Mon, 6 Apr 2009 09:34:03 -0400
> > > > Loui Chang <louipc.ist at gmail.com> wrote:
> > > > 
> > > > > On Mon, Apr 06, 2009 at 02:55:52PM +0200, hollunder at gmx.at
> > > > > wrote:
> > > > > > So this is a bug in yaourt, the second today it seems.
> > > > > > Guess I start hunting for the yaourt and namcap
> > > > > > bugtrackers..
> > > > > 
> > > > > When tracking down bugs please do not pollute your results by
> > > > > relying on unsupported scripts.
> > > > 
> > > > The problem is that even if those scripts are unsupported they
> > > > are widely used (well, namcap not as widely a one could wish).
> > > 
> > > It should be clear if you saw the disclaimer on the AUR home page.
> > > I guess that could be a case to put the disclaimer on every page,
> > > so the point is hammered in. Heh.
> > 
> > Won't help ;)
> 
> What do you suggest? I could delete and/or block yaourt from AUR if
> there are too many support requests to Arch.

I don't suggest anything, just point out reality.
Almost every Arch user uses AUR, many through yaourt.
yaourt, Votes: 1918, certainly far more users than that.
It still is in AUR, not community.


> > Does the AUR webpage and yaourt rely on namcap as well? Both don't
> > get it right either.
> 
> AUR doesn't rely on namcap.

K, thanks, so I have to file another one, hopefully at the right place
for a change.
 
> > '+' bug for yaourt reported here:
> > http://bugs.archlinux.org/task/14122?opened=4326
> 
> Jeez don't file bugs for unsupported scripts. Contact the yaourt
> developers. If you can't get a hold of them then there's nothing that
> the Arch Linux devs can do for you.

For me the case is simple, the yaourt webpage[1] led me to this
bugtracker or at least made it appeared to be the bugtracker, I just
reported the bug. If this is wrong then official Arch and yaourt need
to straighten this out.
No matter if it's unofficial, it's heavily related and as such both
projects should talk to each other.

[1] http://archlinux.fr/yaourt-en


Best regards,
Philipp