On Fri, 20 Jun 2008, Daenyth Blank wrote:
2008/6/20 Ond?ej Ku?era <[EMAIL PROTECTED]>:
On Sun, 13 Apr 2008 02:12:41 -0500
Simo Leone <[EMAIL PROTECTED]> wrote:
On Sat, Apr 12, 2008 at 01:48:58PM +0200, Jan de Groot wrote:
I could update it again. The reason for patching it during froscon
was
2008/6/20 Ondřej Kučera <[EMAIL PROTECTED]>:
> On Sun, 13 Apr 2008 02:12:41 -0500
> Simo Leone <[EMAIL PROTECTED]> wrote:
>
>> On Sat, Apr 12, 2008 at 01:48:58PM +0200, Jan de Groot wrote:
>> > I could update it again. The reason for patching it during froscon
>> > was that upstream azureus doesn't
On Sun, 13 Apr 2008 02:12:41 -0500
Simo Leone <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 12, 2008 at 01:48:58PM +0200, Jan de Groot wrote:
> > I could update it again. The reason for patching it during froscon
> > was that upstream azureus doesn't work with GNU java.
> >
> Why do we care? What's w
On Fri, Jun 20, 2008 at 09:38:42AM -0400, Dale Blount wrote:
> > > +1 on the change from /home, but I don't think /usr/share is the right
> > > place. /usr should be able to be mounted read-only except when software
> > > is changed. That's something you can't do if you keep websites
> > > there.
On Fri, Jun 20, 2008 at 10:27:36AM -0400, Christian Babeux wrote:
> Loui wrote:
>>
>> I'm thinking the bug tracker would be a decent place to record reasons
>> that a package is out dated. Then people could easily bump the ticket
>> with new comments and suggestions, and everyone watching the bug w
Loui wrote:
On Fri, Jun 20, 2008 at 12:04:24PM +0200, Mathieu Clabaut wrote:
[...]
Anyway, in the long term, it would be very nice to be able to publish
somewhere the reason for some package being out dated It may allow
anonymous user to provide some help.
I'm thinking the bug tra
On Fri, Jun 20, 2008 at 3:53 PM, Loui <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 20, 2008 at 12:04:24PM +0200, Mathieu Clabaut wrote:
> [...]
> > Anyway, in the long term, it would be very nice to be able to publish
> > somewhere the reason for some package being out dated It may allow
> > anony
On Fri, Jun 20, 2008 at 12:04:24PM +0200, Mathieu Clabaut wrote:
[...]
> Anyway, in the long term, it would be very nice to be able to publish
> somewhere the reason for some package being out dated It may allow
> anonymous user to provide some help.
I'm thinking the bug tracker would be a de
On Fri, Jun 20, 2008 at 11:50 AM, Jan de Groot <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-06-20 at 11:12 +0200, Mathieu Clabaut wrote:
> >
> > Hello,
> >
> > what is the policy for extra out-of-date packages.
> > I'm thinking about eclipse and antlr
> > The first one gave birth to its AUR up
On Fri, 2008-06-20 at 11:12 +0200, Mathieu Clabaut wrote:
>
> Hello,
>
> what is the policy for extra out-of-date packages.
> I'm thinking about eclipse and antlr
> The first one gave birth to its AUR up to date counterpart :
> eclipse-bin,
> and I've got an antlr3 package at hand, but I
On Fri, Jun 20, 2008 at 11:28 AM, Emmanuel Benisty <[EMAIL PROTECTED]>
wrote:
> On Fri, Jun 20, 2008 at 4:12 PM, Mathieu Clabaut
> <[EMAIL PROTECTED]> wrote:
> > what is the policy for extra out-of-date packages.
> > I'm thinking about eclipse and antlr
> > The first one gave birth to its A
On Fri, Jun 20, 2008 at 4:12 PM, Mathieu Clabaut
<[EMAIL PROTECTED]> wrote:
> what is the policy for extra out-of-date packages.
> I'm thinking about eclipse and antlr
> The first one gave birth to its AUR up to date counterpart : eclipse-bin,
> and I've got an antlr3 package at hand, but I
Hello,
what is the policy for extra out-of-date packages.
I'm thinking about eclipse and antlr
The first one gave birth to its AUR up to date counterpart : eclipse-bin,
and I've got an antlr3 package at hand, but I do not want to make it in AUR
without knowing if it is good practice.
Tho
13 matches
Mail list logo
