[PC-BSD Testing] ports tree auto-update

[Tigersharke .]

On Wed, Dec 14, 2011 at 4:13 PM, Sean Cavanaugh <Millenia2000 at hotmail.com>wrote:

> ‘Portsnap fetch extract’  ??****
>
> ** **
>
> *From:* testing-bounces at lists.pcbsd.org [mailto:
> testing-bounces at lists.pcbsd.org] *On Behalf Of *Tigersharke .
> *Sent:* Wednesday, December 14, 2011 4:42 PM
> *To:* PC-BSD Testing list
> *Subject:* [PC-BSD Testing] ports tree auto-update****
>
> ** **
>
> Howdy,.,
>
> A conversation on IRC lead to this thought..
>
> Currently when a new system is installed, the ports tree (and source) are
> pulled from the install media, and it is unpacked from a tarball.
>
> What I propose, is that the above happens as usual, however:  (contingent
> upon network/repo access)****
>
>    - at first boot or first login, the system updater does a check on the
>    ports tree and updates it (*if* the ports tree was added during install).
>    ****
>    - could system source be 'sketched in' and then obtained at first
>    boot/login?****
>
> With this arrangement, the ports tree is not stale and its freshness is
> not so tied to the release date of the media.  Things like EasyPBI
> (especially once it is available as a PBI itself) will then be able to work
> on the latest ports.
>
> Thanks for your time and interest!****
>
>
Of course portsnap fetch extract (and/or update) would work.

However, an assumption with PC-BSD is ease-of-use and general automation of
tasks.  I was not necessarily suggesting any sort of continual update
process, though that could be done.  What I meant was that at the least,
the first login to a fresh install of PC-BSD, would have the most
up-to-date ports tree.  It may actually use portsnap behind the scenes to
accomplish this.
The reasoning was the expectation by the average user that everything
is/would be current right after install. Many of us are very well aware
that there is a flood of updates due to freezes around release time.
Additionally, I foresee an increased use of things such as EasyPBI, which
necessarily would work best with an up-to-date ports tree.

Actually, now that I've spent more time thinking about it.. it makes a lot
of sense for those who choose to install the ports tree, that it auto
updated on a reasonably regular basis. This is only the tree framework, and
not an update of installed ports in which case there could be issues (as
reported in /usr/ports/UPDATING).

Thanks for your comment!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20111214/b1811c37/attachment.html>