Hi list, after the security announcement (http://www.freebsd.org/news/2012-compromise.html) I use svn to update my local ports tree. I've found out that the port index is not updated. What is the preferred/recommended way to update port indexes when using svn? Thanks, Serguey.
On Mon, Dec 10, 2012 at 06:39:56PM +0400, S.N.Grigoriev wrote:> Hi list, > > after the security announcement > (http://www.freebsd.org/news/2012-compromise.html) I use svn to > update my local ports tree. I've found out that the port index is > not updated. What is the preferred/recommended way to update port > indexes when using svn? >Either 'make index' or 'make fetchindex'. Glen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20121210/518db918/attachment.sig>
On 10/12/2012 14:39, S.N.Grigoriev wrote:> after the security announcement > (http://www.freebsd.org/news/2012-compromise.html) I use svn to > update my local ports tree. I've found out that the port index is not > updated. What is the preferred/recommended way to update port indexes > when using svn?That ports INDEX generated for 'make fetchindex' is not being updated is a temporary thing, while machines are quarantined and rebuilt. So you could just wait for a few weeks until service is resumed. If you just have to have an INDEX before then, then pretty much your only option is to build your own. You can either use 'make index' or ports-mgmt/p5-FreeBSD-Portindex. There are various advantages either way; personally I prefer the latter, but then I'm biased, because I wrote it. Cheers, Matthew
10.12.2012, 18:51, "David Wolfskill" <david at catwhisker.org>:> On Mon, Dec 10, 2012 at 06:39:56PM +0400, S.N.Grigoriev wrote: > >> ?Hi list, >> >> ?after the security announcement (http://www.freebsd.org/news/2012-compromise.html) I use svn to update my local ports tree. I've found out that the port index is not updated. What is the preferred/recommended way to update port indexes when using svn? >> ?... > > First, I've redirected the list recipient from stable@ to ports@, as > this has nothing to do with which branch of the OS you're using, and > everything to do with the Ports collection. > > Second, it also has nothing to do with SVN (vs., e.g, CVS): regardless, > the INDEX is a generated file, and does not come (directly) from the > repository. > > Finally, you can perform "make index" in the ports directory, though > this tends to be time-consuming. ?"make fetchindex" is an alternative, > but the usefulness of that depends on how recently that INDEX was built. > > Peace, > david > -- > David H. Wolfskill david at catwhisker.org > Taliban: Evil men with guns afraid of truth from a 14-year old girl. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key.David, thanks for your detailed explanation. Thanks for all who responded my question. Regards, Serguey.
On Mon, 10 Dec 2012 15:39:56 +0100, S.N.Grigoriev <serguey-grigoriev at yandex.ru> wrote:> Hi list, > > after the security announcement > (http://www.freebsd.org/news/2012-compromise.html) I use svn to update > my local ports tree. I've found out that the port index is not updated. > What is the preferred/recommended way to update port indexes when using > svn?Unless you are a ports committer I recommend you use portsnap to update your ports tree. It takes care of the INDEX file too. Ronald.
On 10 December 2012 09:39, S.N.Grigoriev <serguey-grigoriev at yandex.ru> wrote:> Hi list, > > after the security announcement (http://www.freebsd.org/news/2012-compromise.html) I use svn to update my local ports tree. I've found out that the port index is not updated. What is the preferred/recommended way to update port indexes when using svn? >make index does take a good 20 minutes on a dual core machine, but it's not strictly needed, as pkg_version -vl"<" (or pkg version -vl"<" if you're using the new pkg system) work well, albeit more slowly than if they had an index (as in pkg_version -vIl"<") portmaster doesn't require an index to update stuff. I can't remember if portupgrade does. The index can be [re]built at your leisure while other things are going on (such as rebuilding out-of-date ports), if you don't mind the additional CPU & IO load. -- --