Xin Li wrote:
> > I was going to suggest this too. Isn't this information available
> > using /bin/freebsd-version -u ?
>
> Client side: yes.
>
> Server side: someone has to tell the server to start building for new
> - -CURRENT or stop building for old -STABLE.
Ahhh! Gotcha! Thanks for the qui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/07/15 08:50, Jamie Landeg-Jones wrote:
> Xin Li wrote:
>
>> On 8/6/15 22:24, Kevin Oberman wrote:
>>> Or the code in portsnap could be modified to get the current
>>> running version.
>>
>> I thought about this today but it won't work as ad
Xin Li wrote:
> On 8/6/15 22:24, Kevin Oberman wrote:
> > Or the code in portsnap could be modified to get the current
> > running version.
>
> I thought about this today but it won't work as advertised: someone
> (currently me) still have to tweak the portsnap builder configuration
> to announce
On 08/07/15 09:40, Matthew Seaman wrote:
> Of course, if you're using custom options, then the ports tree you
the ports *INDEX*
D'Oh!
Matthew
signature.asc
Description: OpenPGP digital signature
On 08/07/15 05:11, Kevin Oberman wrote:
> Isn't rebuilding the index useful for people running STABLE? I assume that
> I need a current index to get useful output from "pkg version -vL=". I am
> probably a bit unusual in that I keep a current ports tre on a STABLE
> system, but there are a couple o
On Thu, Aug 06, 2015 at 05:19:54PM -0700, Xin Li wrote:
> Hi,
>
> Currently the default portsnap.conf would generate INDEX-11, INDEX-10
> and INDEX-9. The INDEX file is only used for searching ports, and only
> one (INDEX-${OSREL:R}) file is actually used.
>
This is default behaviour for other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 8/6/15 22:24, Kevin Oberman wrote:
> Or the code in portsnap could be modified to get the current
> running version.
I thought about this today but it won't work as advertised: someone
(currently me) still have to tweak the portsnap builder con
On Thu, Aug 6, 2015 at 9:58 PM, Jamie Landeg-Jones
wrote:
> Kevin Oberman wrote:
>
> > Isn't rebuilding the index useful for people running STABLE? I assume
> that
> > I need a current index to get useful output from "pkg version -vL=". I am
> > probably a bit unusual in that I keep a current po
Kevin Oberman wrote:
> Isn't rebuilding the index useful for people running STABLE? I assume that
> I need a current index to get useful output from "pkg version -vL=". I am
> probably a bit unusual in that I keep a current ports tre on a STABLE
> system, but there are a couple of ports that I ne
On Thu, Aug 6, 2015 at 5:19 PM, Xin Li wrote:
> Hi,
>
> Currently the default portsnap.conf would generate INDEX-11, INDEX-10
> and INDEX-9. The INDEX file is only used for searching ports, and only
> one (INDEX-${OSREL:R}) file is actually used.
>
> Traditionally, we create all supported INDEX-
Hi,
Currently the default portsnap.conf would generate INDEX-11, INDEX-10
and INDEX-9. The INDEX file is only used for searching ports, and only
one (INDEX-${OSREL:R}) file is actually used.
Traditionally, we create all supported INDEX-* files by default, but the
only users who would benefit fro
11 matches
Mail list logo
