Search results

Nice to hear that someone is actually using qbittorrent. :) Were you able to resolve your installation problem?

FYI, mergemaster does not copy files from /usr/obj. The process it uses is described in the mergemaster man page.

You're correct that MASTER_SITE_INDEX, INDEXFILE, and INDEXDIR are the right things to look at, but there is a bit of behind the scenes that you also need to know. The FreeBSD INDEX files are distributed in .bz2 format, so that is what portmater is looking for. If you compress your INDEX file...

If you define PM_SU_CMD=/usr/local/bin/sudo in your portmaster.rc file (and do the other configuration mentioned in the man page) then you can run portmaster as a regular user, and it will only use enhanced privileges when absolutely necessary. FYI, Doug

Yes to both parts of your REPLACE_BASE question. The bind97-sdb port is for use of that version of BIND with postgres or ldap. The bind98 ldap support should work if you pick that option, but I haven't set it up myself so I couldn't make any promises. :) If you run into problems please send...

Someone else already suggested portmaster as your tool to build packages, I will ever-so-humbly state that I agree. :) As long as the infrastructure in the ports tree is correct, using the -g option for portmaster will produce correct packages. The issue of customization is more complex...

This could happen if you've adjusted the OPTIONS locally to something other than the defaults (which are what the FreeBSD packages are built with). You can try make showconfig in editors/vim to see if it's been changed, and make rmconfig to remove any customizations. Hope this helps, Doug

Thanks for the kind words. :)

With +CONTENTS files that contain no useful information this is the only solution. Well done. :)

Actually portmaster doesn't care where the installed stuff came from (ports or packages). It's happy to upgrade whatever you have. Glad you sorted out your problem in any case.

Thanks for the vote of confidence jilles. :) The default behavior for portmaster is to create a backup package of the port before it pkg_delete's it, so the problem described by the OP would not happen. Most of what can be done with /usr/local/etc/pkgtools.conf can be recreated with...

That was mistake number one. :) The first time through using -r or -f you do not use the -R option. Read the man page about what -R does if you're confused as to why. Side note, most man pages are written to be scanned quickly and/or searched. The portmaster man page is designed to actually be...

This happens because if you choose the SASL option in the ldap port it changes the port's name. You've hit upon the right workaround, which is to install the ldap port first. The better solution would be for portmaster to use the same technique that the ports infrastructure uses to detect...

You may also want to look at the 'portmaster -s' feature, which will notify you about ports that were previously installed as dependencies of other ports, but are no longer depended on; and offer to delete them for you. Someone else already pointed out the --list-origins feature, which is...

Warren was kind enough to point this thread out to me, and recommended pkg_delete -a here which I've just updated the svn version of the docs to include. That'll be in the next release. No one can tell you if it's "safe" to do that, you have to use your own judgment. If you're concerned, back...

That's an interesting suggestion, which I will take into account for future versions. FYI, the reason it is written that way is that properly behaving ports should not remove configuration files that the user has modified. Therefore in an ideal world pkg_delete'ing the ports first will...

This process is only needed when you are doing a major upgrade of the FreeBSD version or architecture. Such as 8.x -> 9.x, or i386 -> amd64. You would have been better off with portmaster -a I don't know why that's surprising, it's doing exactly what you told it to do. :) Portmaster has no...

The portmaster -R option Quoting from the man page: I fail to understand how that could be hard to understand. :)

Couple of problems here. :) First, -e does not take multiple ports. I've just updated the svn version to clarify this, and the update will be in 3.2 which will be coming out ASAP. Second, the term "glob" in the portmaster documents refers to a glob pattern, which does not need a * appended on...

FYI, I don't usually read the forums, so your best bet for portmaster questions is freebsd-ports@FreeBSD.org. That all seems fine. I have custom values for WRKDIRPREFIX and PACKAGES myself, and I have used custom values for DISTDIR and NFS mounted my ports tree in the past, all with...