Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Nov 2012 10:27:15 -0500
From:      Greg Larkin <glarkin@FreeBSD.org>
To:        Damien Fleuriot <ml@my.gd>
Cc:        jb <jb.1234abcd@gmail.com>, freebsd-questions@freebsd.org
Subject:   Re: When Is The Ports Tree Going To Be Updated?
Message-ID:  <50B4DBD3.2050901@FreeBSD.org>
In-Reply-To: <CAE63ME5YQ-UJ5z9Mu9-PyxgceK4Gd_oBL4_Pm=e+fp_Z=Mf6_A@mail.gmail.com>
References:  <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org> <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com> <50B2BEE1.9030903@tundraware.com> <loom.20121126T120530-186@post.gmane.org> <05eafe033134e0771d54dec2d9388c8f@homey.local> <loom.20121126T161423-178@post.gmane.org> <C1998C36-57DF-4ACE-8AF2-09E1885E7176@my.gd> <loom.20121126T170433-746@post.gmane.org> <loom.20121126T182635-720@post.gmane.org> <50B3BA6E.7060303@tundraware.com> <loom.20121126T201404-815@post.gmane.org> <CAE63ME5YQ-UJ5z9Mu9-PyxgceK4Gd_oBL4_Pm=e+fp_Z=Mf6_A@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/27/12 4:36 AM, Damien Fleuriot wrote:
> On 26 November 2012 21:15, jb <jb.1234abcd@gmail.com> wrote:
>> Tim Daneliuk <tundra <at> tundraware.com> writes:
>> 
>>> ... One wonders if using svn to keep the ports tree up-to-date
>>> might not be simpler, and perhaps, more reliable ...
>> 
>> As managed by portsnap: $ du -hs /usr/ports/ 850M    /usr/ports/
>> 
>> As managed by svn (it took much longer to checkout/download it by
>> comparison): $ du -hs /usr/local/ports/ 1.4G
>> /usr/local/ports/ $ du -hs /usr/local/ports/.svn/ 702M
>> /usr/local/ports/.svn/
>> 
>> One thing about svn is that it is a developer's tool, with its
>> own commands set (that should never be mixed with UNIX commands
>> w/r to dir/file manipulation), and that should not be expected to
>> be learned by non-devs.
>> 
>> For that reasons alone the portsnap-managed ports repo is more
>> generic, flexible to be handled by user and add-on
>> apps/utilities, looks like more efficient without that svn
>> overhead resulting from its requirements and characteristics as a
>> source control system.
>> 
>> But, svn offers to a user a unique view into ports repo, e.g.
>> history, logs, info, attributes, etc.
>> 
>> jb
>> 
> 
> While we're on the binary vs SVN topic, I'd like to point out I'm 
> *actually running out of inodes* on a virtualized machine (we use 
> these a lot for our dev and preproduction environments) with 5gb
> of space, when checking out the ports tree.
> 
> Of course 5gb is quite small but then, this was installed a while
> back.
> 
> The transition to SVN means I'm going to have to reinstall these
> firewalls. There are a lot of them it's going to be a major pain.
> 
> 
> idk, I'm loathe to use portsnap, I liked CSup just fine.

Unless you plan to use svn commands other than checkout in your ports
tree, I would suggest switching to "svn export" or perhaps the
svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to
fetch your ports tree.

The export command will not create the .svn metadata directory and
will save on inode usage.  Of course, you could also create a new
virtual disk for /usr/ports and tune it with more inodes if you'd
rather use svn checkout.

Hope that helps,
Greg

- -- 
Greg Larkin

http://www.FreeBSD.org/           - The Power To Serve
http://www.sourcehosting.net/     - Ready. Set. Code.
http://twitter.com/cpucycle/      - Follow you, follow me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Darwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlC029MACgkQ0sRouByUApBC5QCfZeDivNGRMWB4DV4usXGLojrv
lBsAoIWG4O/ekYRiGJI0M238v+J1y/Lx
=wHdv
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?50B4DBD3.2050901>