did not understand, more time for what?Your system works as before, it just takes more time.
did not understand, more time for what?Your system works as before, it just takes more time.
For anything the INDEX file was asked before (like the mentioneddid not understand, more time for what?
pkg version -vl '<'
). As you noticed you can create it after every GIT update by yourself (make index
- takes its time, too), or download it (make fetchindex
- but assume that to be faulty when using git/gitup, as it wasn't build upon the files you've fetched, so that isn't really an option).I mean too!For anything the INDEX file was asked before (like the mentionedpkg version -vl '<'
). As you noticed you can create it after every GIT update by yourself (make index
- takes its time, too), or download it (make fetchindex
- but assume that to be faulty when using git/gitup, as it wasn't build upon the files you've fetched, so that isn't really an option).
cd /usr/ports/ && make index
...
--- describe.x11-toolkits ---
--- describe.x11-wm ---
make_index: /usr/ports/databases/p5-AnyEvent-CouchDB: no entry for /usr/ports/databases/couchdb2
Done.
Please read my initial post. INDEX will be wrong in any case. It will possibly be "more wrong" when downloaded instead of locally created. But in a nutshell, you just shouldn't rely on it at all.For anything the INDEX file was asked before (like the mentionedpkg version -vl '<'
). As you noticed you can create it after every GIT update by yourself (make index
- takes its time, too), or download it (make fetchindex
- but assume that to be faulty when using git/gitup, as it wasn't build upon the files you've fetched, so that isn't really an option).
Please read my initial post. INDEX will be wrong in any case. It will possibly be "more wrong" when downloaded instead of locally created. But in a nutshell, you just shouldn't rely on it at all.
That's, unfortunately, wrong. AsUsing the selfmade INDEX just for comparing version numbers of the ports tree and the installed packages is save, flavors do not affect them
makeindex
doesn't consider the flavor when deriving the package name, it will go wrong as soon as you have a package from a non-default flavor.weekly_status_pkg_enable="YES"
pkg_version_index="-P"
-P
is the default if there is no INDEX file, but it’s better to specify it explicitly, just in case an INDEX file happens to be downloaded or generated accidentally.-P
has the nice side effect that orphaned packages will be reported correctly (i.e. port origins that don’t exist anymore), which is not the case when an INDEX file is used.In the context of ports moving to GIT, as well as (expected) deprecation of portsnap, I've seen some questions regarding INDEX, which was automatically fetched by portsnap.
--- describe.x11-servers ---
--- describe.x11-themes ---
--- describe.x11-toolkits ---
--- describe.x11-wm ---
make_index: Circular dependency loop found: php73-pear-Net_SMTP-1.9.0 depends upon itself.
Done.
peter@vps:/home/peter $ ls -l /usr/ports/INDEX-12
-rw-r--r-- 1 root wheel 0 Apr 9 03:39 /usr/ports/INDEX-12
pkg version
to run.… Why will portsnap be deprecated (and when is it expected to happen)? …
… My only use of it is to sometimes find ports, using a package called psearch. …
I don’t know exactly what features psearch provides, but maybe Porgle is useful for you. It’s a web-based search engine for the FreeBSD ports collection. It has low browser requirements, it also works fine with text-based browsers (lynx, w3m, links).
So far I haven’t seen an official statement regarding the deprecation of portsnap, so this is speculation.Why will portsnap be deprecated (and when is it expected to happen)?
The plan to do so is officially announced (portmgr@ hat):So far I haven’t seen an official statement regarding the deprecation of portsnap, so this is speculation.
Yes, of course, I don’t have doubt about the deprecation itself. But since there is no deadline yet, it doesn’t appear that immediate action is required now, or in the near future.The plan to do so is officially announced (portmgr@ hat):
[HEADS UP] Planned deprecation of portsnap
lists.freebsd.org
So, yes, when exactly this will happen is speculation, but it's unlikely to see a 180° turn here.