On Tue, Mar 11, 2008 at 09:53:50PM +, Jacob Meuser wrote:
> so is p, but I _hate_ it when I change a port locally and up the p level,
> and then pkg_add -u downgrades that package.
>
> there's gotta be room for improvement.
Of course. Be patient.
On Tuesday 11 March 2008 17:53:50 Jacob Meuser wrote:
> On Tue, Mar 11, 2008 at 10:23:55PM +0100, Marc Espie wrote:
> > On Tue, Mar 11, 2008 at 05:11:04PM -0400, Brad wrote:
> > > On Tuesday 11 March 2008 16:57:20 Jacob Meuser wrote:
> >
> > > > so, for the rest of the life of these ports, we will
On Tue, Mar 11, 2008 at 10:23:55PM +0100, Marc Espie wrote:
> On Tue, Mar 11, 2008 at 05:11:04PM -0400, Brad wrote:
> > On Tuesday 11 March 2008 16:57:20 Jacob Meuser wrote:
>
> > > so, for the rest of the life of these ports, we will always have to tack
> > > on v0?
> > >
> > > seems (much) less
On Tue, Mar 11, 2008 at 05:11:04PM -0400, Brad wrote:
> On Tuesday 11 March 2008 16:57:20 Jacob Meuser wrote:
> > On Tue, Mar 11, 2008 at 02:47:04PM +0100, Simon Bertrang wrote:
> > > On Tue, Mar 11, 2008 at 11:57:52AM +, Mikolaj Kucharski wrote:
> > > > On Tue, Mar 11, 2008 at 12:05:13AM +
On 2008/03/11 17:11, Brad wrote:
> > so, for the rest of the life of these ports, we will always have to tack
> > on v0?
> >
> > seems (much) less than ideal.
>
> That makes no sense at all. It should be 1.12 -> 1.13 -> 1.12v0 -> 1.14.
How can that work? v# is used to override any higher version
On Tue, Mar 11, 2008 at 05:11:04PM -0400, Brad wrote:
> On Tuesday 11 March 2008 16:57:20 Jacob Meuser wrote:
> > so, for the rest of the life of these ports, we will always have to tack
> > on v0?
> >
> > seems (much) less than ideal.
>
> That makes no sense at all. It should be 1.12 -> 1.13 ->
On Tuesday 11 March 2008 16:57:20 Jacob Meuser wrote:
> On Tue, Mar 11, 2008 at 02:47:04PM +0100, Simon Bertrang wrote:
> > On Tue, Mar 11, 2008 at 11:57:52AM +, Mikolaj Kucharski wrote:
> > > On Tue, Mar 11, 2008 at 12:05:13AM +, Jacob Meuser wrote:
> > > > On Tue, Mar 11, 2008 at 02:22:52
On Tue, Mar 11, 2008 at 02:47:04PM +0100, Simon Bertrang wrote:
> On Tue, Mar 11, 2008 at 11:57:52AM +, Mikolaj Kucharski wrote:
> > On Tue, Mar 11, 2008 at 12:05:13AM +, Jacob Meuser wrote:
> > > On Tue, Mar 11, 2008 at 02:22:52AM +0300, Vadim Jukov wrote:
> > >
> > > > Wow! But... What p
Run it again. The upstream ruby gem servers give sporatic failures.
On 2008 Mar 11 (Tue) at 11:09:39 + (+), Edd wrote:
:Hi,
:
:I am new to using gems, but according to the user manual this should
:work:
:
:---8<---
:# gem query --remote --name-matches qt
:
:*** REMOTE GEMS ***
:
:qtruby
On Tue, Mar 11, 2008 at 11:57:52AM +, Mikolaj Kucharski wrote:
> On Tue, Mar 11, 2008 at 12:05:13AM +, Jacob Meuser wrote:
> > On Tue, Mar 11, 2008 at 02:22:52AM +0300, Vadim Jukov wrote:
> >
> > > Wow! But... What port version did you made diff from?
> >
> > oops. try this instead.
> ..
On Tue, Mar 11, 2008 at 12:05:13AM +, Jacob Meuser wrote:
> On Tue, Mar 11, 2008 at 02:22:52AM +0300, Vadim Jukov wrote:
>
> > Wow! But... What port version did you made diff from?
>
> oops. try this instead.
...
> -PKGNAME= ${DISTNAME}p1v0
...
> +PKGNAME= ${DISTNAME}
Can we remove
Hi,
I am new to using gems, but according to the user manual this should
work:
---8<---
# gem query --remote --name-matches qt
*** REMOTE GEMS ***
qtruby4 (1.4.9)
# gem install --remote qtruby4
ERROR: could not find qtruby4 locally or in a repository
---8<---
User error or a bug?
--
Best
11 March 2008 г. 04:13:02 Jacob Meuser wrote:
> On Tue, Mar 11, 2008 at 03:47:51AM +0300, Vadim Jukov wrote:
> > Applied fully OK now.
> >
> > Some sort of strange results appear. I added "***" comments to a
> > pure terminal grab. All significant pauses (>3s) mentioned (and a
> > few seconds on pl
13 matches
Mail list logo
