Re: Packaging Go Libs
I agree with you. Maybe we should provide helpers to do the "fetching dependencies" part so that will be less cumbersome. On Mon, Apr 17, 2017 at 4:20 PM, Steve Wills wrote: > Hi, > > I'd like to propose eliminating packaging of Go libs. > > Almost every Go app is developed with a different version of any given > lib than what another Go app might use. Forcing a Go app to use a > different version than what upstream might have chosen is error prone at > best and likely to produce a build that's unsupported upstream. So for > the packaged libs to even be useful, we would have to have as many > versions of each lib as there are consumers, or nearly as many. > > Further, best practice in the Go community is for Go apps to vendor all > their dependencies and almost all apps do that. This is the reason most > Go apps use different versions of it's libs. > > So to me, packaging Go libs doesn't make sense and I think we should > remove the Go libs from ports. > > Existing ports which use the Go libs should be updated to not use the Go > lib ports by doing one of these, in priority order: > > * Converted to using vendored deps included with the package source if > possible (preferred) > * Fetching the versions of deps specified by upstream (in the case of > vendor.json) > * As a last resort (deps are not included nor versions specified > exactly) fetching versions of deps available at the time of upstream > development > > Further, documentation should be added to the Porters Handbook saying > that we don't package Go libs and portlint should be updated to check > for installing files in GO_SRCDIR and GO_LIBDIR (exceot lang/go*). > > For reference, here's the list of Go lib ports that I found at the moment: > > archivers/go-compress > databases/gomdb > databases/gosqlite3 > databases/levigo > databases/radix.v2 > databases/redigo > devel/go-bayesian > devel/go-cobra > devel/go-codec > devel/go-cpuid > devel/go-crc32 > devel/go-faker > devel/go-form > devel/go-go.uuid > devel/go-goregen > devel/go-hashicorp-logutils > devel/go-json-rest > devel/go-logrus > devel/go-metrics > devel/go-nuid > devel/go-pflag > devel/go-protobuf > devel/go-raw > devel/go-runewidth > devel/go-slices > devel/go-sql-driver > devel/go-uuid > devel/go-yaml > devel/goprotobuf > net/go-amqp > net/go-geoip > net/go-httppath > net/go-httptreemux > net/go-nats > net/go.net > security/go.crypto > security/goptlib > textproc/go.text > www/go-fasthttp > www/webgo > > Does anyone have any objection or reasoning why this doesn't make sense? > > Thanks, > Steve > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/go 1.7.5 fails to install on Arm
go/pkg/%%opsys_ARCH%%/runtime/cgo.a is in the plist, but for some reason it is not compiled on arm. is it the only error ? On Sun, Feb 5, 2017 at 9:11 AM, Peter Jeremy wrote: > I'm trying to install lang/go on a RPi and it's failing because cgo.a is > missing (see below). Looking through the sources it looks like it should > exist but it's not built and there's no build error. Can anyone clarify > whether the problem is the port or my build environment? (And, if the > latter, does anyone have any suggestions what is wrong?) > > ===> Installing for go-1.7.5,1 > ===> Checking if go already installed > ===> Registering installation for go-1.7.5,1 > pkg-static: Unable to access file /usr/obj/usr/ports/lang/go/ > work/stage/usr/local/go/pkg/freebsd_arm/runtime/cgo.a: No such file or > directory > *** Error code 74 > > Stop. > make: stopped in /usr/ports/lang/go > > -- > Peter Jeremy > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/go security problem on one but not the other
On 9/2/2015 9:49 PM, Kevin Oberman wrote: On Wed, Sep 2, 2015 at 9:31 AM, Rob Belics wrote: The date for vuln.xml, on the server which it won't build on, is September 1 while the date on the other is July 25. OK. So the July 25 system seems to not be updating the vuln.xml file and that file is from prior to the discovery of the vulnerabilities in 1.4.2. First, you need to find out why one system does not seem to be updating the vuln.xml file. It should be updated by /usr/local/etc/periodic/security/410.pkg-audit which is installed as part of pkg. You can try running it manually (as root) to see what the problem might be. Second, you should drop the maintainer of go14, jlaffaye@, a request that he update go14 to 1.4.3. It is quite likely that he is already aware of the issue and just has not gotten it taken care of yet. the vulnerability was first reported on Aug. 28, so it is pretty recent. It is not unlikely that he has been on vacation at this time of the year. There is no such release as 1.4.3. And it is unclear if the Go team would release one as 1.5 is out (they dont support old branches). lang/go14 is only in the PT to bootstrap lang/go, so refusing to build this port because it has security issues in the net package is kind of annoying. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Port version problem
On 3/23/2014 12:05 PM, Jerry wrote: When I ran the following command after updating my port's tree: /usr/sbin/pkg version -vIL= It produced the following output: dri-9.1.7_3,2 > succeeds index (index has 7.6.1_3,2) libEGL-9.1.7 > succeeds index (index has 7.6.1) libGL-9.1.7> succeeds index (index has 7.6.1_4) libdrm-2.4.50 > succeeds index (index has 2.4.17_1) xf86-video-ati-7.2.0_1 > succeeds index (index has 6.14.6_1) xf86-video-intel-2.21.15_1 > succeeds index (index has 2.7.1_6) xorg-server-1.12.4_4,1 > succeeds index (index has 1.7.7_11,1) How is that even possible? I don't recall seeing anything in UPDATING that referred to this. You have to update the INDEX too. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: full documentation for all @'s in pkg-plist
On 11/10/2013 12:47 AM, Aryeh Friedman wrote: Where would I find a complete list of @'s allowed in pkg-plist and hopefully an explination of each one? (the porter's handbook is incomplete) In the manpage pkg_create(1). ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: NEED_ROOT
On 10/4/2013 11:45 PM, Paul Schmehl wrote:
From my reading it appears that one of the goals of STAGE is to allow
users
to build and install ports under their UID. Are the perms in
/usr/ports changing?
In testing the port that I'm working on, I find that I do not have
rights to write to /usr/ports/distfiles and I do not have rights to
write to ${WORKDIR}. That pretty much precludes building the port
unless your root. No surprise there since the files in /usr/ports are
owned by root:wheel.
So are the perms going to change? Is port building going to run
setuid? Or is this a vaporware?
Well... set WRKDIRPREFIX and DISTDIR to point somewhere writable by your
user.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_info -W equivalent in pkgng?
pkg which On 8/5/2013 9:01 PM, Xin Li wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Is there an equivalent of pkg_info -W with pkgng? (Or let's say, given a file /usr/local/bin/X, how do I find the corresponding package that installs it?) Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJR//adAAoJEG80Jeu8UPuzsTUIALkvHHkxlpCcuBp4PRtCiC/U AATOufv7E2uGUUbQCCWwx7JoQ2c7QpnxgIhMIVbcveFfoJ27Pik5Qfnmaip5ozCD m6WKjk1OhJcDosshfpSU3nSJet5AeB501oFg9y31/3s+TDqZr+Cu9LFx85Ktyzhu M7IObwY76XKUC/s1xU1SkEz4NO74afhoejnCQxMkCteYFZNEZGvToZH+ckLoqljZ IyLpBSYZybooV9Ei29+qGIRnbmdR7uEcdzTiRjLKHPqDaotnbhxRYjiVcLHrHxZ2 U/hwmEO7RYbJa9fIfykZGKcrHTEigzeiR6VDqwGExR847XFZ70o/XsBbpl7PjZQ= =2KHr -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg info list sources?
On 4/18/2013 8:46 AM, Diane Bruce wrote: On Wed, Apr 17, 2013 at 11:23:35PM -0700, Beeblebrox wrote: I want a list of all installed packages in the form category/port. I will feed the list to poudriere. $ pkg info -ao > pkg.list gives a list but needs cleaning - gcc-4.6.3: lang/gcc How can I remove the left part of the colon and keep the trailing bit? pkg info -ao |cut -f 2 -d ' ' - Or use pkg-query(8) ;) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_version: the package info for package '...' is corrupt
On 4/2/2013 10:30 PM, Ronald F. Guilmette wrote: Ok, first, my apologies to Leslie Jensen about the e-mail bounce. It is nothing personal, believe me. I just have a personal policy of locally blacklisting any and all domains that send me spam. (Apparently, at one time or another, I received some spam from bjare.net.) I believe that if _everybody_... or even just 10% of everybody... did as I do, then ISPs would finally take seriously their spam outflow problems. (Most of them don't at present, and that explains why there is so much spam.) Now, as regards to "pkg_version" versus "pkg version" I have never even seen the latter, so I don't know a damn thing about that. Furthermore, although there does appear to be an executable named /usr/sbin/pkg present on my system, whatever the heck it is, it does not seem to have any associated man page. :-( So anyway, I have never used it, I don't know what it even does, and I would still not know how to use it, even if you held a gun to my head. Regarding Julien Laffaye comment(s) relating to "pkgng", I have also never even heard of that before now. What is it and where do I get it? And if it is so wonderful... and if what I am using is considered "old"... then why isn't this new "pkgng" thing the default in/on 9.1-RELEASE? (I also apparently have no man page for anything called "pkgng" on my system.) https://wiki.freebsd.org/pkgng /usr/bin/pkg is the binary that will bootrap pkgng, installing the real binary and manpages. Anyway, athough I do thank both Leslie Jensen and Julien Laffaye for their comments and attempts to help, I still am in DIRE need of an answer to my original question. I have, apparently, over 50 of my installed ports that pkg_version is now telling me are in some *unspecified way* "corrupt" and I still need (and am desperately begging for) someone to tell me how to resolve that problem, exactly. As I have said, I _do_ have a recent full system backup, but that doesn't help me unless and until someone tells me which file or files from that, exactly, I should be restoring in order to eliminate this problem. Could someone kindly do that, please? You can try ports-mgmt/portmaster, which has some options to try to repair the /var/db/pkg database. If the backup is fresh and you did not install new packages since, you can just copy the /var/db/pkg from the backup to the system (backup-ing the broken one, we never know, you might need it...) Regards, rfg P.S. I do most seriously wonder if whoever engineered the FreeBSD ports system ever realized how dramatically UNhelpful a message like the following actually is: pkg_version: the package info for package 'evince-2.32.0_9' is corrupt I do not intend to offend anyone, but to be frank, this is the kind of a message I would expect out of a Windows system, i.e. a message that some- thing is broken, but providing -zero- details regarding what exactly is broken, where it is located, or, most importantly, how to begin to fix the problem. When I am using Windows, I _expect_ to be treated like a luser... i.e. one who cannot be trusted with too much information. When I am using any kind of *NIX system however, I tend to expect the exact opposite, and am rather unhappy when critical information is hidden from me. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_version: the package info for package '...' is corrupt
On 4/2/2013 11:41 AM, Leslie Jensen wrote: 2013-04-02 11:08, Ronald F. Guilmette skrev: [[ I asked about this problem on the -questions list a couple of days ago, but didn't get any relevant replies, so I'm trying again here on the -ports list. Apologies if you see this twice. ]] A couple of days ago my system just simply decided to power itself off (twice) whilst I was in the middle of doing "portupgrade -a". I have since learned that the unscheduled and unexpected power offs were due to a CPU cooling problem. I believe that I have that problem in hand now. Separately however, and probably as result of the sudden power offs, when I run pkg_version now I am getting many messages relating to various of my installed packages, all having the following general form: pkg_version: the package info for package 'PKG' is corrupt where `PKG' is the name of some package or another that I have installed. I have at least 6 such messages for different packages I have installed... and probably more. I googled around a bit and did not find any good explanation for the above error or, more importantly, what to do about it. I gather however that my package data base has become corrupted. OK, so how does one rebuild that from scratch? Please don't tell me that I have to reinstall every bleedin' port from scratch! Regards, rfg P.S. Oh! And by the way, I just happen to have made a full system backup quite recently. Do I just simply need to get the entire contents of /var/db/pkg/ from that backup, and then do "rm -fr /var/db/pkg" and then copy my backup copy of /var/db/pkg to the real /var/db/pkg ? Will that fix the problem? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Are you using pkg? If so the command should be pkg version without the underscore. No, this is the old pkg_version which produces this output. With pkgng, the database is atomic thanks to sqlite, thus this problem would not have occured. /Leslie PS: Your private mail address bounces. I've tried two different SMTP Servers! : host server1.tristatelogic.com[69.62.255.118] said: 550 5.7.1 : Client host rejected: bjare.net is BLACKLISTED - Use http://www.tristatelogic.com/contact.html (in reply to RCPT TO command) <<< 550 5.7.1 : Client host rejected: cust.bredband2.com is BLACKLISTED - Use http://www.tristatelogic.com/contact.html 550 5.1.1 ... User unknown <<< 554 5.5.1 Error: no valid recipients ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg upgrade - Nothing to do
On 11/11/2012 12:26 PM, Alex Keda wrote: HP# uname -a FreeBSD HP.lissyara.su 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Fri Jan 6 17:33:37 MSK 2012 lissy...@hp.lissyara.su:/usr/obj/usr/src/sys/GENERIC amd64 HP# grep -v ^# /usr/local/etc/pkg.conf packagesite: http://pkgbeta.FreeBSD.org/freebsd:9:x86:64/latest HP# pkg upgrade Updating repository catalogue Repository catalogue is up-to-date, no need to fetch fresh copy Nothing to do HP# pkg version -v | grep -v up-to-date apache-ant-1.8.3_1 < needs updating (port has 1.8.4) ca_root_nss-3.13.6 < needs updating (port has 3.14) ... more than 20 lines skipped thunderbird-i18n-16.0.1< needs updating (port has 16.0.2) xf86-input-mouse-1.7.1 < needs updating (port has 1.7.1_1) xterm-284 < needs updating (port has 286) HP# == how I can upgrade software, using pkg? The repository is not up-to-date. pkg version compares against the local ports tree. You can 1) Wait till the repository is updated if you want binary upgrades 2) Compile your ports like you would have done without pkgng (with the ports tree and your tools configured to use pkgng of course). +++ and, some DNS problem, with hosts described in pkg.conf HP# host pkg.FreeBSD.org HP# HP# host pkg.FreeBSD.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: HP# pkgng does not use the A record of the DNS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [patch] Portaudit and PKGNG
On 9/10/2012 9:27 AM, Stefan Esser wrote: PR ports/171406 contains a patch I submitted to make portaudit work with PKGNG: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171406 It works on my systems, but definitely needs further review. The patch just replaces "pkg_info" by "pkg info" and "pkg_version" by "pkg version". This works fine, since PKGNG apparently supports all the required options and kept the output format unchanged compared to the old framework. Regards, STefan Are you aware of pkg-audit(8) ? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: current pkgng situation
On 9/2/2012 1:18 PM, Jamie Paul Griffin wrote: Hi I want to start using pkgng but from reading posts on this list it sppears there are still some tweaks required, as would be expected with a project like this. So, my question is: is it stable enough to start using now on my stable/9 system? I don't mind having to deal with the occasional problem here and there with suuport from ports@ users. I Also want to start using poudriere as well which I understand works well with pkgng. Any comments and/or guidance would be much appreciated. Best wishes, Jamie. What are you referring to ? You can indeed use it :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 9/1/2012 7:43 PM, Tijl Coosemans wrote: On 31-08-2012 14:22, Baptiste Daroussin wrote: On Fri, Aug 31, 2012 at 08:10:50AM -0400, John Baldwin wrote: On Friday, August 31, 2012 5:59:10 am Baptiste Daroussin wrote: On Thu, Aug 30, 2012 at 01:02:06PM -1000, Doug Barton wrote: I agree with John on all counts here. Further, the idea of a self-installing package, at least for the pkg stuff itself, addresses the issue that someone else brought up about how to handle installation of pkg by the installer for a new system. I like the idea of also providing a self-installing package, and it seems really easy to do, so I'll try to see what I can do in this area I'll wrote a PoC in 5 minutes which looks pretty good, this could also be a very simple and easy way to integrate into bsdinstaller. I'll do work in that direction. Still it doesn't solve the problem of boostrapping pkgng in a fresh new box, because the user may not know where to download the pkg-setup.sh. I do think that is something bsdinstall should be able to handle, and I would certainly want bsdinstall to include a dialog that says "do you want to install the package manager?" Of course this is being worked on by dteske@ on his bsdconfig scripts, so yes in anycase the bsdinstaller will end up with a boostrap dialog to install pkgng. Something else I thought of, you can't assume there's a working internet connection during installation. And also, even if there is a connection, can you guarantee that the downloaded pkg supports the packages on the dvd for the lifetime of the release? The packages set included on the dvd will probably be EOLed before the lifetime of the release. I really think you should just do vendor imports of pkg in base and include pkg on the dvd. There's no bootstrap problem then and the dvd is nicely self-contained. It also shouldn't be a problem to keep the official pkg repo for that release compatible with it. Just keep using the same version of pkg to create the repo. You've been able to develop and introduce pkgng without breaking older releases which shows having pkg tools tied to releases was never a problem. All that was needed was to move pkg development outside base. You should be able to do pkg 2.0 development in the same way. And when that new version is ready you import betas and release candidates in head and use current users as testers, just like is done with clang. In this scenario the ports tree needs to keep support for older releases, but that's a consequence of the fact that there's only one ports tree for all releases. Somewhere in between the ports and the various releases there has to be some form encapsulation, not just for pkg, but for all the tools used by the ports tree. Given how the ports tree currently encapsulates both the old and new pkg tools I don't see how supporting multiple versions of pkgng would be a problem because presumably the difference between pkgng versions is going to be much smaller than the difference between the old and new tools. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Script to set/unset "automatic" status in PKGNG database
On 8/30/2012 11:19 PM, John Nielsen wrote: I today noticed the "pkg autoremove" command for the first time, which does much the same thing as pkg_cutleaves but relies on the "automatic" flag in the pkgng database rather than user input to determine which "leaf" ports can be removed. Unfortunately, the pkg2ng utility has no way of knowing which old-style packages it converts were installed automatically as dependencies, so they are all marked as non-automatic (i.e. user-requested). In my case, this was not true for the majority of installed ports. Since I really like this functionality, I decided to update my local package database to match my preferences. Having succeeded, I decided a tool to make doing so easy could well benefit others (as well as my future self). (Plus I wanted an excuse to play with dialog(1) and "pkg query" a bit.) So here's the result. I'm not too attached to the name. It shouldn't eat your package database or steal your lunch money, but I'm not responsible if it does. Other than that, feedback is welcome. JN You want to use `pkg set -A` :) We make zero promises concerning the SQL schema in pkgng so it can change at every time and break your script. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PR 171155
On 8/29/2012 9:39 AM, Stefan Esser wrote: I have created PR ports/171155 to report the issue, that ports with long PLISTs cannot be deinstalled with PKGNG: http://www.freebsd.org/cgi/query-pr.cgi?pr=171155 Regards, STefan Already fixed in the git repository (commit 34c1b4f8b21376dfd270779d118cde4a1d0a62e9) :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 8/24/2012 11:57 PM, Doug Barton wrote: On 8/23/2012 8:03 PM, Eitan Adler wrote: On 23 August 2012 22:59, Doug Barton wrote: I tend to agree with Steve here ... we can't be responsible for other people's poorly written docs. This isn't about poorly written docs. This is the user expecting a tool to exist, which doesn't. Take another example of a sysadmin which rarely installs new systems, installs FreeBSD for the third time, and then gets confused when "pkg install vim" fails. Aren't we going to install the pkg package on new systems when they are installed? Isn't that (shouldn't that be?) part of the project plan? It would be insane for us not to do that, at least for the releases where pkg is the default. True. But when you create jails without the installer, you have to install pkgng by hand. Hence the /usr/sbin/pkg bootstrap. You bring up a valid point that we should keep in mind for our own however. The bootstrapping issue will be the smallest possible annoyance on a long road of the migration process. The bootstrapping issue is a factor even after the migration :) I think that the point I'm trying to make is that it shouldn't be. note that I'm not talking about the mechanism here, I'm trying to avoid "pkg doesn't seem to be installed on my fresh system" becoming a FAQ. The way that we avoid that problem is not to create it for ourselves in the first place. :) The role of pkg-bootstrap is for those users who have already-installed systems that need to do the conversion, or if somehow pkg becomes corrupted on the user's system and needs to be reinstalled. That's it. I like that you're thinking through the related issues, but in this particular case I think you're overthinking it. Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 8/24/2012 3:57 AM, Eitan Adler wrote: On 23 August 2012 18:19, Steve Wills wrote: Hi, It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying "I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to." Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. no opinion on the name, but imho there should be *something* called "pkg" on a fresh system. Users will install a new system, follow some random how-to, and not realize they missed a step. If the default package errors with exit code 1 and says "run pkgbootstrap first" that is okay too. Ideally, pkgng bootstrap process will be part of the bsdinstall steps (using the pkg package tarball on the installation media). The bootstrap tool is in base (instead of only on the install media) essentially for installations without the installer (like creating jails). So its true that in these case you have to think to run the bootstrap command. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng default schedule... registering a few reasons for rethinking the final implementation...
On 8/23/2012 6:26 PM, Jeffrey Bouquet wrote: I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. cd /var/db/pkg ls -lac | grep py26 ls -lac | grep python as the more simple example. With due respect to its developers and the persons who agree that the package tools could be upgraded, the mandatory usage of a front-end database to a file directory one is here viewd as mutt-only-mbox, registry-and-bsod rather than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; ... I see concurrently too few tests on lower-end p2, p3 as to whether pkg can run with lesser memory machines (routers...) (pfsense) Everyone's is welcome to help us with that! The memory usage can be decreased by using gzip over xz for (un)compression. ... I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, pfsense..) due to less-reliability, more-possibility of bugs.. If we get useful detailed bug reports, we will fix 'em! ... Not to mention native tab-completion not dependent upon further customizations, ... Introduces complexity to running earlier versions of BSD virtualized in later versions and vice versa... ... I've innumerable times made "quick work" (2 hours or so) of cross-disk backup/fix/upgrade using /var/db/pkg where doing so with just the pkg tools or my own scripts would take immeasurably longer... Why ? ... It would deprecate searching +CONTENTS, for example, or quickly checking the text file +REQUIRED_BY without a database frontend. ... Almost every reply and post have glossed over those points, referring to the benefits of a newer package management system, again glossing over the added memory requirements, number of .so. required, lack of extensive testing across all hardware cpu/memory scenarios... ... "it will be a single tool that will do the job of all the many port/package management scripts currently only available in the ports system (bsdadminscripts)" for example. A single tool, yes. But it won't do all of the edge-case jobs *not* covered by the present pkg_ tools that can be crafted hooking into the /var/db/pkg/ directory structure, with find for example. "pkgng is not a replacement for portmaster or portupgrade..." That was not my question. My concern was with the deprecation of the latter and /var/db/pkg along with the introduction of pkgng. ... Each pkg_ legacy uses about 3-6 .so. afaik. pkg uses 19. 18 :) ... A review of pkgng on mebsd.com, suggests replacment CLI for tasks one might do with portmaster now. However, they are much more arcane (%H-%M vs -g...) and thus unwelcoming... ... "patches for portmaster and portupgrade to use pkgng tools" Memory requirements with both working together? The ABI between them breaks? ... My concerns are more or less, why should the following *ever* be mandatory... "On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by "install" and/or "mtree" dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via pkgng only depends on lib in the base system. Why was libarchive.so missing? portmaster or via core dumping install. By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install and mtree didn't coredump and it worked - and this procedure rescued me. But on my lab's development box, it didn't work! " (Continues with more equally terrible detail...) (Freebsd-questions, august) ... Or my own experience, today, testing on a p4 pre-p2 memory req. investigations. # pkg stats Unable to open remote database "repo". Try running 'pkg update' first. # pkg update Updating repository catalogue zsh: segmentation fault pkg update Do you have useful details about this segv, like a backtrace ? . So, a kernel option (non default) to deprecate /var/db/pkg? A further development of pkg to concurrently maintain a /var/db/pkg? ...not implying the concurrent deprecation of the latter! Brighter ideas? Thanks for reading these concerns. I am quite perturbed by the announcement of v11 erasing the /var/db/pkg upon which I presently use daily numerous times... And I apologize, in advance, for typos etc. herein... J. Bouquet 2004 v5... Regards, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On 7/20/2012 9:24 PM, Vitaly Magerya wrote: Julien Laffaye wrote: Yes it is needed at runtime if you are a developper using sqlite3 and pkg-config: to use `pkg-config sqlite3 --cflags` and `pkg-config sqlite3 --libs` in your $APP build process. It's $APP that needs pkg-config as a build dependency. Sqlite3 does not need to depend on pkf-config at all; it should install .pc file and nothing more. Look at lang/gcc, lang/python or devel/pcre: they all do it this way. In short, sqlite3 should completely drop the dependency on pkg-config. I am not trying to state what it should or should not do. I am trying to guess why it is doing things like it does. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On 7/20/2012 9:03 PM, Kimmo Paasiala wrote: On Fri, Jul 20, 2012 at 9:50 PM, Julien Laffaye wrote: On 7/20/2012 8:36 PM, Reko Turja wrote: Its use is not limited to Gnome, as you can see it's used in the build process of databases/sqlite3 and there are many other ports that have nothing to do with Gnome that use it the same way. The only thing that is wrong with it is that ends up being a run time dependency of sqlite3 instead of being only a build time dependency. Maybe this could be changed, anyone know if it's possible? Actually, sqlite3 builds and works quite fine with pkg-config dependency removed from makefile. So it's kinda silly to pull it in by force - of course it's not pkgng problem, but a problem in the port itself. sqlite3 installs "/usr/local/libdata/pkgconfig/sqlite3.pc". So I think the rationale is if a developper wants to link against sqlite3 using the pkg-config file, he should have pkg-config on his machine. If you go this way, you could also ask why sqlite3 install header files which are not needed for the runtime dependency (when what is required is only the shared object)... This could be handled by having pkg-config only as a build time dependency for sqlite3 and for any port that depends on it, pkg-config is a build time tool much like autoconf, automake, libtool etc. and is not needed to use the port at run time. Yes it is needed at runtime if you are a developper using sqlite3 and pkg-config: to use `pkg-config sqlite3 --cflags` and `pkg-config sqlite3 --libs` in your $APP build process. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On 7/20/2012 8:36 PM, Reko Turja wrote: Its use is not limited to Gnome, as you can see it's used in the build process of databases/sqlite3 and there are many other ports that have nothing to do with Gnome that use it the same way. The only thing that is wrong with it is that ends up being a run time dependency of sqlite3 instead of being only a build time dependency. Maybe this could be changed, anyone know if it's possible? Actually, sqlite3 builds and works quite fine with pkg-config dependency removed from makefile. So it's kinda silly to pull it in by force - of course it's not pkgng problem, but a problem in the port itself. sqlite3 installs "/usr/local/libdata/pkgconfig/sqlite3.pc". So I think the rationale is if a developper wants to link against sqlite3 using the pkg-config file, he should have pkg-config on his machine. If you go this way, you could also ask why sqlite3 install header files which are not needed for the runtime dependency (when what is required is only the shared object)... Just hoping that in pkgng there would be some "Yes I might shoot myself in foot, but sod it" -options. Well, if you really want to shoot yourself, you can edit the local db with sqlite. On the other hand, based on experience with 2 boxes running pkgng+portupgrade experimentally for some days pkgng looks like pretty good backend. Just still with some minor nits. -Reko ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng team: please update portmaster patch to 3.13.1
On 7/17/2012 2:49 PM, Anton Shterenlikht wrote: The 3.13 patch fails in 7 places. Sorry for not using github One good reason to integrate the patch with upstream is that it would avoid us this unpleasant work of updating the patch after every release. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make {run,build}-depends-list vs. pkg_info -r?
On 6/10/2012 1:22 PM, Ben Laurie wrote:
I am confused...
In audio/squeezecenter, I get:
# make {run,build}-depends-list
/usr/ports/archivers/p5-Compress-Zlib
/usr/ports/audio/faad
/usr/ports/audio/flac
/usr/ports/audio/mac
/usr/ports/audio/sox
/usr/ports/converters/p5-Encode-Detect
/usr/ports/converters/p5-JSON-XS
/usr/ports/databases/mysql50-client
/usr/ports/databases/mysql50-server
/usr/ports/databases/p5-DBD-mysql
/usr/ports/devel/p5-Time-HiRes
/usr/ports/graphics/p5-GD
/usr/ports/lang/perl5.8
/usr/ports/net/mDNSResponder
/usr/ports/security/p5-Digest-SHA1
/usr/ports/textproc/p5-XML-Parser
/usr/ports/textproc/p5-YAML-Syck
/usr/ports/www/p5-HTML-Parser
/usr/ports/www/p5-Template-Toolkit
/usr/ports/databases/mysql50-client
/usr/ports/lang/perl5.8
/usr/ports/sysutils/p5-File-Which
but:
# pkg_info -r squeezecenter-7.3.3
Information for squeezecenter-7.3.3:
Depends on:
Dependency: expat-2.0.1_2
Dependency: openssl-1.0.1_2
Dependency: mDNSResponder-333.10
Dependency: mp4v2-1.9.1
Dependency: libvpx-1.0.0
Dependency: perl-5.8.9_7
Dependency: p5-YAML-Syck-1.19
Dependency: p5-XML-Parser-2.41
Dependency: p5-HTML-Tagset-3.20
Dependency: p5-HTML-Parser-3.69
Dependency: p5-Digest-SHA1-2.13
Dependency: png-1.5.10
Dependency: jpeg-8_3
Dependency: gpac-libgpac-0.4.5_6,1
Dependency: x264-0.123.2189_2
Dependency: pkg-config-0.25_1
Dependency: opencv-core-2.3.1_4
Dependency: freetype2-2.4.9_1
Dependency: gd-2.0.35_8,1
Dependency: p5-GD-2.46_1
Dependency: p5-common-sense-3.4
Dependency: p5-Time-HiRes-1.9725,1
Dependency: p5-AppConfig-1.66
Dependency: p5-Template-Toolkit-2.24
Dependency: orc-0.4.16
Dependency: schroedinger-1.0.11
Dependency: libltdl-2.4.2
Dependency: p5-DBI-1.621
Dependency: mysql-client-5.0.95
Dependency: p5-DBD-mysql-4.021
Dependency: mysql-server-5.0.95
Dependency: p5-JSON-XS-2.32
Dependency: p5-Encode-Detect-1.01
Dependency: libiconv-1.14
Dependency: mac-3.99.4.5_1
Dependency: libogg-1.2.2,4
Dependency: libvorbis-1.3.3,3
Dependency: libtheora-1.1.1_2
Dependency: libmad-0.15.1b_2
Dependency: libid3tag-0.15.1b
Dependency: libao-1.1.0_1
Dependency: lame-3.99.5
Dependency: gsm-1.0.13
Dependency: flac-1.2.1_2
Dependency: libsndfile-1.0.25_1
Dependency: faad2-2.7_3,1
Dependency: faac-1.28_2
Dependency: ffmpeg-0.7.12_2,1
Dependency: sox-14.3.2_4
Dependency: p5-IO-Compress-Base-2.015
Dependency: p5-Compress-Raw-Zlib-2.054
Dependency: p5-IO-Compress-Zlib-2.015_1
Dependency: p5-Compress-Zlib-2.015
Why are the dependencies so different? e.g. the p5*Compress* ones...
What's going on?
pkg_info shows the complete dependencies, and not only the direct
dependencies.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to uninstall pkgng
On 6/9/2012 8:23 PM, Jason Hellenthal wrote: On Sat, Jun 09, 2012 at 07:03:23PM +0100, Matthew Seaman wrote: On 09/06/2012 18:46, Marcin Wisnicki wrote: I've made a mistake of installing pkgng on 9.0-amd64 but since there is no up-to-date repository I want to remove it. What would be the correct procedure to achieve that ? Invoking `pkg delete -a` still leaves some files including /usr/sbin/pkg. Not easy. You'ld have to delete the pkg port, undo any additional configuration you may have added to eg. /etc/make.conf (ie. remove WITH_PKGNG settings), undo any patches to portmaster (if you're using that) and then reinstall all your ports using the original package tools to rebuild /var/db/pkg/ contents. /usr/sbin/pkg is part of base nowadays. You don't want to delete that. When was pkgng made part of base ? The bootstrap binary is in base, not pkgng. /usr/sbin/pkg would be from pkgng if you are using it to delete itself then the problem you are experiencing is the file is busy at the time of deletion. Try pkg_delete instead ? Wrong, this is the bootstrap binary. The pkg binary is in LOCALBASE. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to uninstall pkgng
On 6/9/2012 7:46 PM, Marcin Wisnicki wrote: I've made a mistake of installing pkgng on 9.0-amd64 but since there is no up-to-date repository I want to remove it. Have you looked at http://pkgbeta.freebsd.org/freebsd-9-amd64/latest/ ? What would be the correct procedure to achieve that ? Invoking `pkg delete -a` still leaves some files including /usr/sbin/pkg. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng problems
On 05/16/12 13:13, Ivan Voras wrote: Hi, I attempted to try pkgng, and failed: 1) I would like to request some documentation be added in the ports-mgmt/pkg port, to the pkg-message file, instructing to set up the pkg.conf (by copying the pkg.conf.sample file) before starting to do anything with pkgng. I would also like to request this same documentation added to the FAQ at https://github.com/pkgng/pkgng/blob/master/FAQ.md#0, and that the error message "pkg: PACKAGESITE is not defined" be changed to e.g. "pkg: PACKAGESITE is not defined - pkg.conf not found" or something similar indicating how to solve the problem. Well, it can also be an environment variable. 2) The pkg.conf.sample file does not contain a list of valid repos: repos: default : http://example.org/pkgng/ repo1 : http://somewhere.org/pkgng/repo1/ repo2 : http://somewhere.org/pkgng/repo2/ ... and apparently this makes running "pkg update" impossible as it exits with the completely useless error message "Broken pipe". At least this error message should be changed. I will have a look. I would like to request that pkg.conf.sample contain valid repos by default. While at it, where on the web is the list of valid repos and why is the documentation (README and the .sample conf file) not referencing it instead of specifying the abstract "example.org" addresses? Well, we have a repo for testing: pkgbeta.freebsd.org but it is not endorsed by portmgr or something like that. Plus, this repo is temporary and can/will disappear. But we can add it during the testing phase. (I know pkgng is not finished, but this way you are not going to get any enthusiastic testers...) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating lang/go to version 1?
On 4/24/2012 9:24 PM, Maxim Khitrov wrote: The Go programming language version 1 was released on March 28th. Are there plans to update the port, which is currently still using the 20111017 release? Carlo Strub submitted a patch for this, but I'm not sure if it's ready to go or still being tested: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/166934 - Max It does not compile on i386. I reported an issue: http://code.google.com/p/go/issues/detail?id=3452 But as there is no progress, I plan to commit it for amd64 only. Also, there are ports using the old version of Go which need to be updated. I updated most of them and have to get maintainers approval so I can leave the Ports Tree with fully working golang package just after go1 hit the tree. Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg check -a doesn't work
On 4/16/2012 10:18 PM, Anton Shterenlikht wrote: On Mon, Apr 16, 2012 at 03:04:00PM -0500, Bryan Drewery wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/16/2012 10:09 AM, Baptiste Daroussin wrote: On Mon, Apr 16, 2012 at 03:46:04PM +0100, Anton Shterenlikht wrote: # pkg check -a usage: pkg check [-yadsr] pkg check [-ygxXdsr] For more information see 'pkg help check'. # According to the man page, this should've worked, by processing all packages. -a is for processing all packages, it should be used with one of the possible actions: -d -s -r Maybe the manpage is not really accurate. Can you open an issue about this problem? regards, Bapt Anton, I've logged this here: https://github.com/pkgng/pkgng/issues/199 I'm working on a usage/manpage update for it. I've started the pr already: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/166997 We work with github issues and not with PRs as pkgng is developed outside officials FreeBSD source repositories. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg audit segfault
On 04/16/2012 04:21 PM, Anton Shterenlikht wrote: pkg audit -F On my 9.0-RELEASE amd64, it works fine. BTW, did you manage to upgrade your local database? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng beta 11: pkg-static: The database is outdated and opened readonly *** Error code 74
On 04/16/2012 11:03 AM, Anton Shterenlikht wrote:
On Mon, Apr 16, 2012 at 09:20:41AM +0100, Anton Shterenlikht wrote:
Updating ports-mgmt/pkg to b11:
===> Installing for pkg-1.0.b11
===>Generating temporary packing list
===> Checking if ports-mgmt/pkg already installed
pkg-static: The database is outdated and opened readonly
*** Error code 74
Stop in /usr/ports/ports-mgmt/pkg.
Please advise
Looking at the bit which issued the error:
# grep -C3 "The database is outdated" ./work/pkg-1.0-beta11/libpkg/pkgdb.c
while (db_version< DBVERSION) {
if (!sqlite3_db_readonly(db->sqlite, "main")) {
pkg_emit_error("The database is outdated and opened
readonly");
return (EPKG_FATAL);
}
db_version++;
#
I decided to update sqlite3, only to discover
that I can no longer do it:
# make -C /usr/ports/databases/sqlite3
/usr/local/sbin/pkg: not found
===> License unknown accepted by the user
===> Found saved configuration for sqlite3-3.7.11
===>sqlite3-3.7.11 depends on file: /usr/local/sbin/pkg - not found
===> Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg
===> Installing for pkg-1.0.b11
===>Generating temporary packing list
===> Checking if ports-mgmt/pkg already installed
pkg-static: The database is outdated and opened readonly
*** Error code 74
Stop in /usr/ports/ports-mgmt/pkg.
*** Error code 1
How can I recover from this?
Is it a good idea to switch to
the old tools for recovery?
pkgng does not use the ports's sqlite but its own version. Updating the
sqlite port has no effect on pkgng.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng beta 11: pkg-static: The database is outdated and opened readonly *** Error code 74
On 04/16/2012 10:20 AM, Anton Shterenlikht wrote: Updating ports-mgmt/pkg to b11: ===> Installing for pkg-1.0.b11 ===>Generating temporary packing list ===> Checking if ports-mgmt/pkg already installed pkg-static: The database is outdated and opened readonly *** Error code 74 Stop in /usr/ports/ports-mgmt/pkg. Please advise The database schema changed so pkgng try to upgrade it. But here pkgng does not have rights to do so. Try re-run pkgng as root. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg version -Xs foo shows all ports, not just foo
On 4/11/2012 8:16 AM, Wayne Sierke wrote: On Tue, 2012-04-10 at 13:47 -0700, Greg Byshenk wrote: On Tue, Apr 10, 2012 at 08:55:41PM +0100, Anton Shterenlikht wrote: BUZI> pkg version -Xs Image CalculiX-2.4 = GraphicsMagick-1.1.15_3,1 = ImageMagick-6.7.5.10 = ORBit2-2.14.19 = OpenEXR-1.6.1_3= R-2.14.2 = ^C BUZI> The man page seems to indicate that the above options should only show ImageMagick. What am I doing wrong? Is it a transcription error or are you really using a command named "pkg" rather than pkg_version(1)? I think he is using pkgng. I'm not sure if it's a bug or a feature, but pkg_version seems to want the arguments separately. $ pkg_version -X -s Image ImageMagick = $ Works ok here: $ uname -v ; pkg_version -Xs "lib[Xx]c" FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57 UTC 2011 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC libXcomposite = libXcursor = libxcb = $ %uname -v ; pkg_version -Xs "lib[Xx]c" FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:07:27 UTC 2011 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC libXcomposite = libXcursor = libxcb = %pkg_version -Xs Image ImageMagick = % ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: BUILD_DEPENDS and libraries -- how to express build-time-only dependency on library?
On 4/1/2012 2:58 PM, Lev Serebryakov wrote:
Hello, Ports.
In case of static build of ported program, port need to have
BUILD_DEPENDS on libraries. LIB_DEPENDS is not suitable here, because
inc ase of static linkage, there will no dependency on livbrary in
runtime.
But BUILD_DEPENDS search for files at absolute pathname or for
executables.
Is it possible to express build-time-only dependency on library?
BUILD_DEPENDS=${LOCALBASE}/lib/libfoo.a:${PORTSDIR}/foo/libfoo ?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP] pkgng 1.0-beta9 please test
On 03/30/2012 01:10 PM, Lars Engels wrote: On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote: Hi, On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 [...] Please note that normally this will be the last beta version, So we can expect an official package repository with the first RC? A public repo, maybe. An official repo endorsed by portmgr that's another story... :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg2ng duplicate file listing warnings
On 03/12/2012 05:48 PM, Anton Shterenlikht wrote: Running pkg2ng on r231193M ia64 gave these warnings: Registering CalculiX-2.4... pkg: duplicate file listing: /usr/local/share/doc/CalculiX/ccx/node580.tml, ignoring Registering binutils-2.22_1... pkg: lstat(/usr/local/bin/ld.gold): No such file or directory Registering docbook-4.4_2... pkg: duplicate directory listing: /usr/local/share/doc/docbook/4.4/, inoring Registering docbook-4.5_2... pkg: duplicate directory listing: /usr/local/share/doc/docbook/4.5/, inoring Registering font-bh-ttf-1.0.3... pkg: duplicate directory listing: /usr/local/lib/X11/fonts/TTF/, inoring done. Registering font-misc-ethiopic-1.0.3... pkg: duplicate directory listing: /usr/local/lib/X11/fonts/TF/, ignoring pkg: duplicate directory listing: /usr/local/lib/X11/fonts/OTF/, ignoring done. Registering font-misc-meltho-1.0.3... pkg: duplicate directory listing: /usr/local/lib/X11/fonts/OT/, ignoring done. Registering openldap-sasl-client-2.4.26... pkg: duplicate directory listing: /usr/local/etc/openlda/, ignoring done. Registering pkg-config-0.25_1... pkg: duplicate directory listing: /usr/local/lib/pkgconfig/, ignorng done. Shall I chase these up with the respective ports maintainters? Yes, pkgng is more strict :) Or are these false positives? Or perhaps bugs in pkgng? Well, they should not :p ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Beta 3 still not OK
On 2/11/2012 2:13 AM, Sergio de Almeida Lenzi wrote: Seems that the sqlite database has changed from beta1 to beta3??? I have all the system running exclusive on pkg there is no more "old pkg" How can I upgrade the sqlite database from beta1 to beta3??? There is nothing to upgrade. The on-disk format of the sqlite database is frozen by the sqlite guys and they are very conservative about that. We just upgraded the code to have latest bugfixes and improvements. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP][CFT] pkgng beta1 is out
On 02/10/2012 10:24 AM, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:20:47AM +, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are>400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. So do I understand correctly that once switched to pkg(1), the old pkg_* tools should not be used anymore? Is that what the output below tells me: # pkg version -v |grep "<" gcc
Re: [HEADSUP][CFT] pkgng beta1 is out
On 02/09/2012 11:20 AM, Anton Shterenlikht wrote: On Thu, Feb 09, 2012 at 10:17:10AM +0100, Alberto Villa wrote: On Thursday 09 February 2012 10:02:31 Anton Shterenlikht wrote: There are>400 ports installed, so I'm still missing something else. You didn't run pkg2ng. thanks again. I missed that too. Is this somewhere in pkg man pages? I didn't see it. It is a one time operation when you are coming from the old pkg_install, so it is not in the manpage. While running pkg2ng I get: Registering pkg-config-0.25_1... pkg: duplicate directory listing: /usr/local/lib/pkgconfig/, ignoring done. Should I be worried? No. Is the plan to merge pkg-config into pkgng? No. Thanks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Perl symlinks question
On 1/9/2012 8:42 PM, Eitan Adler wrote:
On Mon, Jan 9, 2012 at 2:36 PM, Ruslan Mahmatkhanov wrote:
Eitan Adler wrote on 09.01.2012 23:32:
2012/1/9 Chris Rees:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
/usr/bin is in LOCALBASE which may be read only.
Ok, but if so most part of ports tree will not build on such systems,
because automake tools (aclocal in particular) calling /usr/bin/perl.
The option should remain on by default due to the majority use case,
but elimination the option is a bad idea. Users should not have to
hack ports to use a readonly LOCALBASE.
Last time I installed perl with /usr/bin readonly (ezjail) it failed
silently to create the symlink so there is really no reason to switch
this option off.
That's why, I would also go for option 2/
If you have a readonly /usr/bin, it is the job of your administrator
(that'd be you!) to create the symlink.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to handle config files
On 1/8/2012 1:59 PM, Martin Kropfinger wrote: Hi there! The porters handbook describes a way to handle config files: http://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html It is recommended to do it this way for keeping changed files after deinstallation on the system. But the example is not really clear to me. What does this line do: @exec if [ ! -f %D/etc/orbit.conf ] ; then cp -p %D/%F %B/orbit.conf; fi Nothing is said about those variables... %D (which seems to be %%PREFIX%%) and %F or %B. Have a look at pkg_create(1) manpage ;) Can anyone give me some help? Thanx a lot! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_version and portversion: ports version comparison weirdness
On 12/18/2011 17:43, Conrad J. Sabatier wrote: Can anyone explain why I'm seeing the following? libX11-1.4.99.1
Re: [CFT] pkgng alpha2
On 12/13/2011 06:16 PM, Andriy Gapon wrote: on 30/11/2011 22:32 Julien Laffaye said the following: [1] : https://github.com/pkgng/pkgng/issues [2] : https://github.com/pkgng/pkgng [3] : http://wiki.freebsd.org/pkgng [4] : http://people.freebsd.org/~bapt/pkgng-bsdcan2011.pdf [5] : http://wiki.freebsd.org/201110DevSummit/Ports?action=AttachFile&do=get&target=pkgng-devsummit.pdf [6] : http://wiki.freebsd.org/201110DevSummit?action=AttachFile&do=get&target=pkgng-devsummit-track.pdf Couple of questions/suggestions: 1. Do you plan to have a pkgng port to issue the preview releases pkgng? Current pkgng installation/bootstrap procedure is really easy, but the port would be even more convenient for prospective testers. Yes, this is planned. The ports will bootstrap pkgng. 2. Is there a public pre-built package repository with pkgng-format packages that could be used for testing and getting a taste of a packages-only pkgng-managed system? Unfortunately, no. I think I now have the resources to do that for the next CFT. But it will only be 9.0 amd64 I am afraid. We cant build packages for the entire matrix. Thank you. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[CFT] pkgng alpha2
Hi all, We are releasing pkgng (the next pkg_install) alpha2 to the world and we want you to test it! There is no "good" method to test it: use it as you would in the real world. Of course, you are encouraged to backup your data or test it in some kind of virtualized environment. After using it for some time, you will certainly find bugs. You can report them on the issues tracker [1]. If you find missing features, that is things you can't do with pkgng but can with pkg_install, you can also report them. New features are not the expected outcome of this call, as we want to release a final version ASAP. FYI, an alpha3 should follow shortly to fix issues in alpha3 and test additional features. After that, there will be a feature freeze with beta1. Getting started: You can download or git clone the source code of pkgng on the github page [2]. Then, a boring `make' followed by `make install' will do it. If you have some packages installed by pkg_add, you can convert the old database to the pkgng database with the 'pkg2ng' shell script in the ports/ folder. You can also add packages from the ports tree (with bsd.pkgng.mk) or with a pkgng repository. All is documented in the README and manpages. If you are a newcomer to pkgng, this doc reading step is also valuable to us. Indeed, if you fight to get the right infos, or if some things feel counter intuitive, we should improve it! Which brings me to the topic of contributing to pkgng. The best thing you can do is to write down the documentation you would have loved to read while testing pkgng! And of course, if you have a patch with your bug report, it is much appreciated. If you read this entire mail and wonder what is this pkgng thing, you can read the wiki page [3], bapt's presentation from BSDCan [4], EuroBSDCon [5] [6] and browse the source code. Regards, Julien, on behalf of the pkgng team. And remember, we _do_ want to hear back from you! Please also note that it is still alpha code and it can kill kitten and puppies. You are warned ;-) [1] : https://github.com/pkgng/pkgng/issues [2] : https://github.com/pkgng/pkgng [3] : http://wiki.freebsd.org/pkgng [4] : http://people.freebsd.org/~bapt/pkgng-bsdcan2011.pdf [5] : http://wiki.freebsd.org/201110DevSummit/Ports?action=AttachFile&do=get&target=pkgng-devsummit.pdf [6] : http://wiki.freebsd.org/201110DevSummit?action=AttachFile&do=get&target=pkgng-devsummit-track.pdf ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/yajl: => Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/lloyd-yajl-2.0.1-f4b2b1a.tar.gz, fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/lloyd-yajl-2.0.1-f4b2
On 11/27/2011 5:15 PM, O. Hartmann wrote: The recently updated port devel/yajl is not building due to the lack of a tarrball: ===>>> Starting build for ports that need updating<<<=== ===>>> Launching child to install devel/yajl ===>>> Port directory: /usr/ports/devel/yajl ===>>> Starting check for build dependencies ===>>> Gathering dependency list for devel/yajl from ports ===>>> Dependency check complete for devel/yajl ===> Cleaning for yajl-2.0.1 ===> Vulnerability check disabled, database not found ===> License BSD accepted by the user => lloyd-yajl-2.0.1-f4b2b1a.tar.gz doesn't seem to exist in /usr/ports/distfiles//. => Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch ftp://ftp.cn.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.cn.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/bapt/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch http://files.etoilebsd.net/yajl/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: http://files.etoilebsd.net/yajl/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: Not Found => Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/lloyd-yajl-2.0.1-f4b2b1a.tar.gz fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/lloyd-yajl-2.0.1-f4b2b1a.tar.gz: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles// and try again. *** Error code 1 Stop in /usr/ports/devel/yajl. ===>>> make failed for devel/yajl ===>>> Aborting update ===>>> Update for devel/yajl failed ===>>> Aborting update Regards, Oliver Looks like the mirrors did not... mirror the file yet! Wait n see. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: testing PKGNG
On 09/13/2011 23:16, Michel Talon wrote: Sergio wrote: I moved all my servers (about 40) to the pkgng (new generation) package/port system, and I can say that it is amazing... it is not yet finish, and have some minor "issues", but works very well, and is lightning fast.. It is almost the same as "pacman" (from Archlinux).. you build a "repository" and install packages from that repository. when you update the repository, the other servers can do an "upgrade".. you do not have to have the ports tree in each server, and you build the ports only on the master server in the master server, there is a full gnome2 (with 842 dependencies) that install right on the shelf with only one command: pkg install gnome2 now I have a full functional server runing gnome, libreoffice, inkscape hplip, cups printing, gdm... in about 30 minutes from internet I am extremely interested by what you are saying here. Do you mean that you can find somewhere precompiled packages that you can install in 30mn or that you use packages compiled on a master server? Of course the difference is that if you have just one machine in the basement instead of a server farm, the point of view is not the same ... There are no official mirrors with pkgng packages yet. So I assume he built his packages then deployed them with pkgng. By the way if you mention that pkgng shares something to some penguinist system, beware it will be villified by some guardians of the orthodoxy who are quite vocal. Anyways if it is indeed fast it will make a happy difference with the present pkg-* tools. It is indeed inspired by the competition ;p ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: testing PKGNG...
On 09/13/2011 03:53, Sergio de Almeida Lenzi wrote: Hello, I moved all my servers (about 40) to the pkgng (new generation) package/port system, and I can say that it is amazing... it is not yet finish, and have some minor "issues", but works very well, and is lightning fast.. It is almost the same as "pacman" (from Archlinux).. you build a "repository" and install packages from that repository. when you update the repository, the other servers can do an "upgrade".. you do not have to have the ports tree in each server, and you build the ports only on the master server in the master server, there is a full gnome2 (with 842 dependencies) that install right on the shelf with only one command: pkg install gnome2 now I have a full functional server runing gnome, libreoffice, inkscape hplip, cups printing, gdm... in about 30 minutes from internet Sergio... I am glad to see that it works well for you. But I want to emphasize that this is still experimental code! With 40 machines, I guess you have the biggest pkgng installation out there, so you will certainly find bugs quicker than others. We definitely want to know about them! Thank you for your feedback! Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ports system quality
On 09/02/2011 12:04, Kurt Jaeger wrote: Hi! http://pkgin.net/ [...] pkgin is known to work and have been tested under the following platforms [...] So, what do you actually mean by this? Probably just this: What about trying to port pkgin for FreeBSD, so that pkgin can also be used on FreeBSD ? We are working on pkgng[1], which is a complete rewrite of pkg_install instead of a higher level tool on top of it. Stay tuned for the alpha2 announcement. If this solves the binary pkg-install problem in a generic way on many plattforms (I have not looked at the implementation), that might be a nice feature. [1]: https://github.com/pkgng/pkgng ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: exist status of pkg_info -O
On 08/01/2011 22:38, Andriy Gapon wrote: pkg_info -q -O missing/port exits with status of 0. Not sure if this complies with usual conventions for this kind of tools. No, but the ports tree expect this. While doing pkgng testing, we discovered that we needed to add a dirty workaround to always return 0. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for testers -- CONF_FILES variable
On 07/03/2011 16:30, Eitan Adler wrote: > (I hope this isn't bikeshedding) > > I would much prefer this method over choosing an unusual suffix. There > is much documentation on the internet that assumes certain things > about packaging. Many times INSTALL files will tell the user to > looking for a .sample file or .conf file. It would be odd and annoying > to have the sample configuration file on certain versions of FreeBSD > be different than everyone else. Also, as others have stated, pkgconf > sounds like something FreeBSD specific - not a application specific > suffix. > > As a general note: why does pkgng care about the file suffix at all? > The pkg program should just be "dumb" about it and follow whatever the > pkg-plist says to do. The .pkgconf suffix tells pkgng that this file is a sample. But it could also be done via an attribute. Doing stuff with @exec or scripts should be for special cases, not for common cases such as config files. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for testers -- CONF_FILES variable
On 06/30/2011 08:22, Chris Rees wrote: >> >> I like the rest, but I do not like the name of .pkgconf. I think, the >> 'pkgconf' is best define for something related with FreeBSD rather >> than third-party product. The .sample or .default is best name and >> less confuse for the users, because the word said it all what it is. > > Thanks for the feedback. > > I'm afraid any problems with the .pkgconf sample will have to be > discussed with the pkgng team and bapt@ -- wasn't my choice either. > > Chris Yes, right now, pkgng uses the .pkgconf suffix to know that it is a configuration file. But now, we have a new format for the package manifest so _maybe_ (it has to be discussed with bapt) we can add an attribute to a file entry saying "I am a sample of a conf file". The hardest part for that would be to detect in the ports tree if we are using pkgng or the legacy pkg_install, and, depending on that, to generate the appropriate entry in the manifest / plist. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Tue, Mar 29, 2011 at 5:15 AM, Tim Kientzle wrote: > II. Package signing. That would be really nice. >>> >>> Right know we only planned to sign the repo database, so we can trust >>> the sah256 of the packages stored in the database. Then if the package >>> has the same sha256 as the one in the repo database it is considered >>> trusted. >>> If we want a per-package signing, we would have a tarball in a tarball. >> >> I really expected this to have been mentioned already, but this approach >> (tarball in a tarball) is taken by Debian packages, and I don't remember >> hearing of any issues related to it. I don't think it's worth discounting >> from the start without giving some considerationg, but I will defer to the >> people actually doing the work. > > If you use libarchive-style streaming, it's even > pretty straightforward to read and extract such > things without having to create a bunch of > temporary files. > > You just need to be careful about compression. Agreed, if we dont want to verify the signature, we can extract the tarball in the tarball efficiently. But to verify the signature, we have to read the tarball in the tarball twice: the first time to compute the digest and verify the signature, the second time to do the real extraction. So I guess that the tarball containing the real package archive and the signature should be uncompressed. The real package archive would be compressed, though. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Mon, Mar 28, 2011 at 6:59 PM, Garrett Cooper wrote: > On Mon, Mar 28, 2011 at 10:44 AM, Andriy Gapon wrote: >> on 25/03/2011 12:11 Baptiste Daroussin said the following: >>> Hi all, >>> >>> miwi@ launched the new thing called Experimental Call For Testing, >>> it's our turn :) >>> >>> Julien Laffaye (jlaffaye@) and I, helped by Philippe Pepiot (huge >>> contributor) have been working since the end of the last GSoC on a >>> rewrite of pkg_install. >>> >>> pkgng is a binary package manager written from scratch for FreeBSD. >>> >>> After a long period of technology testing, (json, tinycdb, bdb, etc) >>> and we now have achieved to implement the basic functionnality. We >>> would greatly approciate to have some feedback, wider testing, >>> patching, documenting etc, before implementing the higher level >>> features. >>> >>> pkgng is built on top of a new libpkg, which allow to deal with the >>> database of >>> installed packages, to deal with remote repositories, manage packages: >>> creation, installation gathering informations, registering new ports. >>> >>> features supported are or will be : >>> >>> - smooth integration with bsd.port.mk (including bsd.pkg.mk line 2486) >>> which allow to have a bsd.port.mk which deal with both pkg_install >>> and pkgng. (done in alpha) >>> >>> - the register command can analyse elf files when registering a new port to >>> discover forgotten dependencies if necessary. (done in alpha using libelf) >>> >>> - the register command has two mode available : when dealing with old >>> fashion ports it just registers the package, in new mode it does >>> everything that would >>> have been done by pkg add when installing the package : should display >>> messages, execute post-install, execute @exec etc. (old fashion done >>> in the alpha) >>> >>> - pkg add supports two mode : the old fashion one (no real upgrade >>> support) and new one: upgrade scripts supported. (old fashion in the >>> alpha) >>> >>> - new scripts supported +PREINSTALL +POSTINSTALL, +PREDEINSTALL, >>> +POSTDEINSTALL, +PREUPGRADE, +POSTUPGRADE as well as the old fashion >>> scripts : +INSTALL +DEINSTALL +UPGRADE (all supported *UPGRADES aren't >>> supported in the alpha) >>> >>> - new +MANIFEST (plist-like format) with new metadatas : options, arch, os >>> version, etc. (done in the alpha) >>> >>> - pkgng supports checking arch of the package which means that users >>> won't be able to install sparc64 binary package into amd64 machines. >>> (not done yet) >>> >>> - a special architecture "all" allows to specify when a package can be used >>> on every architecture. (not done yet) >>> >>> - @dirrm and @dirrmtry are now deprecated, pkgng can discover itself >>> which directory has to be removed. (done in the alpha but needs love >>> :)) >>> >>> - new repository (apt-like feature) (only the repository generation is done) >>> >>> - real support for reverse dependency (no ugly +REQUIRED_BY) (done in the >>> alpha) >>> >>> - test unit (libcheck) on libpkg. (done in the alpha needs some more love) >>> >>> - many more >> >> Perhaps I am too impatient :) but I would like to inquire about the following >> features: >> >> I. A provides/requires interface for packages. >> Each package specified a list of files (and perhaps other entities) that it >> provides and requires. At the initial stage, without ports modifications, >> these >> could be: (1) a list of all files installed by package for provides; (2) for >> requires - an auto-generated list of dependencies based on required shared >> libraries plus dependency specifications in ports. >> I think that this kind of interface should help with using alternatives that >> provide the same interface (e.g. like gamin vs fam). Adding require/provide support in pkgng is kind of trivial. But ports have to support it first. >> >> II. Package signing. > > That would be really nice. Right know we only planned to sign the repo database, so we can trust the sah256 of the packages stored in the database. Then if the package has the same sha256 as the one in the repo database it is considered trusted. If we want a per-package signing, we would have a tarball in a tarball. > >> III. Package naming that includes architecture, majo
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 10:11 AM, Baptiste Daroussin wrote: > Developpement site: http://git.etoilebsd.net/pkgng/ FYI, we moved to github[1] in order to have a bug tracker, pull request and code review. Also, I recommend to build from the HEAD of the git repository, to not report fixed compilation warnings/bugs. [1]: https://github.com/pkgng/pkgng ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
On Fri, Mar 25, 2011 at 2:38 PM, Alexander Leidinger wrote: > Quoting Baptiste Daroussin (from Fri, 25 Mar 2011 > 15:14:52 +0100): > >> 2011/3/25 Alexander Leidinger : >>> >>> Quoting Baptiste Daroussin (from Fri, 25 Mar 2011 >>> 11:11:11 +0100): >>> pkgng is a binary package manager written from scratch for FreeBSD. >>> >>> I didn't had a look at it, just some comments about some parts you >>> explained. >>> features supported are or will be : > - a special architecture "all" allows to specify when a package can be used on every architecture. (not done yet) >>> >>> What if a package is able to install on a subset, e.g. the linuxulator >>> ports >>> are for amd64 and i386? >>> >> >> No clue for that at the moment but we are open to suggestions. > > The suggestion is easy, allow a way to specify a set of valid architectures. That looks reasonable and easy to implement. > >>> What about DB corruption/loss? Do you keep the /var/db/pkg//xxx >>> files even with pkgng and only use the DB as a way to speed up some work >>> (so >>> the DB corruption just requires to run pkg2ng), or are you lost of the DB >>> is >>> lost? >>> >> >> Nothing is done about DB corruption/loss, I am not sure we need to do >> something. >> Maybe. > > I would say "for sure". Info: In Solaris 10 sqlite is used for the service > managenemt framework (SMF). It is possible that the DB is corrupt in some > bad situations. In this case you have to rebuild the DB (script provided, > been there, had to use it). If sqlite is properly used with transactions, it is very hard to corrupt the database. But if hardware lies to us and say that the data is on disk whereas it isnt... what can we do? Another potential problem is fsync(), but if it is broken on FreeBSD we want to fix it! BTW, the goal is to only have the database and not the flat files. If you are paranoid about power outage, use something like zfs snapshots... > >> Currently a filesystem corruption/loss on /var/db/pkg would do the same. > > Put a corruption of /var/db/pkg/xyz-1/+REQUIRED_BY would only affect a small > part, and this part could be even recovered from (pkgdb from portupgrade is > able to do it). With sqlite we have atomicity! And locks! > >> but it is sqlite so we can perhaps provide a way to get compressed >> dump so user can periodically backup their database. > > It needs to be automated. Maybe periodic daily... but maybe this is not > often enough after a day of a lot of changes (think about it this way: do > you want to lose a day of changes?). The current FS based DB is very robust, > partly because there is redundant data, pertly because losing a file just > means that the very limited subset of information is lost (and a reinstall > of one port will fix it). > > Bye, > Alexander. Regards, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xf86-video-ati 6.14.0 crashes System
On Sun, Feb 27, 2011 at 4:39 PM, Heino Tiedemann wrote: > Hi There, > > after update tu the new xorg on my FreeBSD8 my system crashes all time > I start X. > > There is no mouse responding (no light in the mouse), the screen turns > black and the system is not respondig by keybord. > > There is only a way out by hard-reset. > > The advice in UPDATING makes no fifference: > > "Section "Device"" > Option "int10" "on" > Option "BusType" "PCIE" > Option "RenderAccel" "on" > Option "AccelMethod" "exa" > Option "DynamicPM" "on" > Option "DRI" "on" > > > System: FreeBSD 8.2-PRERELEASE #0: Thu Feb 3 23:46:34 CET 2011 > > > > Video-Card: > > drm0: on vgapci0 > info: [drm] AGP at 0xf400 64MB > info: [drm] Initialized radeon 1.31.0 20080613 > info: [drm] Setting GART location based on new memory map > info: [drm] Loading R300 Microcode > info: [drm] Num pipes: 1 > info: [drm] writeback test succeeded in 1 usecs > > > The old driver works fine: xf86-video-ati613-6.13.2 > > > Are trhere any logs arround, if the System freezes? Look into /var/logs/Xorg.0.log FYI, I had the same problem. Try to update your ports tree and rebuild the driver to see if it fix the problem. (some files were commited after the big xorg commit because they were forgotten). If you built your video driver without the patches, it may be the origin of your problem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_info -g not working for unprivileged user + unreadable files
On Mon, Feb 7, 2011 at 9:11 AM, Florent Thoumie wrote: > On Mon, Feb 7, 2011 at 7:52 AM, Doug Barton wrote: >> flz, >> >> In r206043 you converted fexists() in src/lib/libpkg/file.c to use open() >> instead of lstat(). Unfortunately this has the side effect of breaking >> 'pkg_info -g' for unprivileged users with files that have no +r bits. For >> example: >> >> pkg_info -g sudo-1.7.4.6 >> Information for sudo-1.7.4.6: >> >> Mismatched Checksums: >> pkg_info: /usr/local/bin/sudo doesn't exist >> pkg_info: /usr/local/bin/sudoedit doesn't exist >> pkg_info: /usr/local/bin/sudoreplay doesn't exist >> pkg_info: /usr/local/sbin/visudo doesn't exist > > How can you compute the checksum if you don't have read access? > I understand that the error message should rather be "Cannot open %s". > >> Reverting your change produces the expected behavior. So my questions are, >> why was the change made, what are its benefits, and how can we fix this >> problem? :) > > I'm sure there was a good reason at the time. I'll have a better look later. I guess that it is related to the problem where the symbolic link exists but the file pointed by the symlink does not. Why open() and not stat(), I don't remember. > > -- > Florent Thoumie > f...@freebsd.org > FreeBSD Committer > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
On 11/29/2010 23:40, Matthias Andree wrote: You can specify limits during compression, so the question is should we do that so that hosts with N MB of RAM can decompress packages? Do we retain the compression ratio over bzip2 if we limit compression memory to 512 MB so that decompression would be possible with, say, 128 MB? According to xz(1), in its default mode (-6), xz uses ~100MiB for compression and ~10MiB for decompression. That seems to be acceptable. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libsoup
On 11/26/2010 01:16, ajtiM wrote:
Hi!
I installed libsoup with portmaster (update) but whenever I run portmaster -a
every time I installed libsoup again.
Code:
The devel/gir-repository-libsoup port moved to devel/libsoup
Reason: merged into libsoup
As I red on FreeBSD forum I ran a:
grep "^...@pkgdep" /var/db/pkg/*/+CONTENTS | awk '{ if (NF != 2) { print $1 } }'
| cut -d':' -f1
and I reinstall K3b-KDE4 but after portmaster -a there were libsoup again.
In the /usr/ports/devel I have
gir-repository and gir-reposit-libnotify still.
After suggestion on FreeBSD forum I ran:
pkg_delete -f gir-repository-libsoup-0.6.5_5
and reinstall libsoup again but now I have a problem with dependencies:
===>>> Updating dependency entry for libsoup-2.32.1 in each dependent port
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> devel/gir-repository-libsoup is listed as a dependency
===>>> but there is no installed version
===>>> Try portmaster --check-depends
===>>> Re-installation of libsoup-2.32.1 complete
and
pkg_info | grep libsoup
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
pkg_info: corrupted record (pkgdep line without argument), ignoring
libsoup-2.32.1 A SOAP (Simple Object Access Protocol) implementation in C
libsoup-gnome-2.32.1 A SOAP (Simple Object Access Protocol) implementation in
C
pkg_info: corrupted record (pkgdep line without argument), ignoring
Thanks in advance.
Did you try ``portmaster --check-depend'' ?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: what next for the pkg_install rewrite
On Fri, Aug 20, 2010 at 12:00 PM, Ivan Voras wrote: > > And... both ideas are completely wrong. SQLite can be imported as a > single C file + header, which you must agree is practically the > optimum, and its license is "public domain" which is, if anything, > "freer" than BSDL and eminently compatible with it. > > And if we don't want to build a sqlite.so which can conflict with the version from ports, we can statically link libpkg to it. Incognito. > BDB in base offer exactly one (1) single "feature", if you can call it > that: storing and retrieving key-value binary blobs. It has no > practical concurrency support, it's locking is laughable and upgrading > data stored as binary blobs is even more nightmarish than maintaining > the current plist format (and it will lead to similar uglyness soon - > rather than upgrading the data piece called "x", I'm sure developers > will introduce new keys called "x_extdata", "x_moredata" etc etc). > If we are going key-value storage, I think that TinyCDB is worth a look. > > SQLite on the other hand solves all these in the following way: > > 1) stores proper records, not blobs > 2) has proper locking & concurrency support, ACID > 3) the database schema can be modified on the fly for upgrading - > fields can be added to existing table while preserving data. > 4) is endian-agnostic, 32/64-bit agnostic and portable (I mean the > database file) to an extremely large number of platforms. It is > already used as a system database in OS X, iPhone and Android. > > Note that I'm promoting SQLite to replace the /var/db/pkg/* tree of > directories and files with ad-hoc structure - all data in there should > be in one SQLite database, which is stored in a single file. > Indeed, all this points can help. The major drawback of SQLite, in my opinion, is the inclusion of long SQL statement in c code. So if we are going this way, we must have strict rules to avoid "polluting" the source. > [...] > > As for backward compatibility: basically it can be done in two ways: > 1) build a one-time converter that will read the present plist > database and output a new database or 2) build a compatibility layer > which would support both the old and the new format at the same time, > so people upgrading will continue to use their old data. I consider > the latter wasteful in terms of developer resources and because > bit-rot will eventually make support for the old format decrepit. > Agreed, a one time converter seems to be the solution. Especially if the transition occur between two major FreeBSD version (say, 9 - > 10). > > > 2. XML is a bad idea. Great in theory, wonderful in my browser, but a > > bloated plaintext file with a lot of complexity. I would prefer a > > database solution that could be dumped to a simple text file format if > > needed. > > XML, at least in my proposal, would not be used for the system package > database, but would replace (either in part or all with a single file) > today's "+" files in the packages, together with other purposes where > some metadata transfer is required. > > That said, I would also be happy with other self-described formats > like JSON. XML is the front runner because it's more standard > (industry standard, whether someone likes this fact or not!) and there > is already a parser in base. > The pro of XML here is that we have a parser in base, The con is its verbosity. But anyway the manifest is not meant to be human readable. Nevertheless, I prefer JSON, because it's less complex than XML and we can have a parser/emiter in a single 500SLOC .c file. And it looks sexier than XML, eh : http://pastebin.com/8hzPSSJC ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: what next for the pkg_install rewrite
On Thu, Aug 19, 2010 at 4:38 PM, Bapt wrote: > Hi, > > Now that GSoC is over a lot of good work has been done on pkg_install. > > I think it would be great to organize the way the on going work on > pkg_install > will be done, for that purpose we need someone to officially manage the > work, to > validate what will be implemented/cleanup, and distribute the work among > volunteers. > > I think this is the best way for a new pkg_install really appear. > > I'd like to contribute to the work on pkg_install, and would like to > help cocordinate the effort to prevent reinventing the wheel, and to be > ensure the code is consistent etc. > > I know there are many like minded people out there who might like to help, > please identify > yourself, either publicly or privately so we can put together a team to > find a pkg_install > replacement. > Hello, I agree: we need to create a task force to work on pkg_install and thus create a dynamic. The very first step of such a team will be to brainstorm: what do we want to achieve? what can be improved? There are a lot of areas of potential discussions: packing list format, local database format, ... In my opinion, trying to be 100% compatible with the actual tools will slow down the project. I am thinking, for example, about the slave/master modes which made sense when we used a temporary directory, but less if we want to extract the files to their final destination via libarchive. Then, this specification will need to be approved by portmgr@ so the actual coding can start! Best regards, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Drop maintainership
On Wed, Jul 28, 2010 at 3:35 PM, Toni Gundogdu wrote: > I can no longer maintain the following ports: > > * multimedia/abby > * multimedia/cclive > * multimedia/clive > * multimedia/clive-utils > * multimedia/quvi > * multimedia/umph > > Perhaps someone reading this list could take them over. > > clive-utils could be removed from the collection, altogether. > The project's been inactive for well over a year now and there > have not been any plans to revive it. > > In any case, please remove my email from the above ports. > Thanks. Hi, I am willing to take maintainership of multimedia/cclive. Best regards, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to determine the history of a port
Hello, On Sun, May 23, 2010 at 4:46 PM, Paul Hoffman wrote: > Greetings again. A few years ago, I proposed editors/emacs-nox11 and > submitted a patch to create it, and thus became listed in the comments at the > beginning of the Makefile (but I am not the package maintainer, I believe). > Today I got a report that the package does not build; I verified this. I want > to help the user, but I have no idea how the change that broke the build was > added to the Makefile. > > How do I find the history so I can find out who added the problematic line > and figure out what they actually meant? You can find the CVS history via : - cvsweb at http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/Makefile - freshports at http://www.freshports.org/editors/emacs-nox11/ Regards, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portmaster: printing messages that do not come from pkg-message files
2010/1/2 Nikola Lečić : > Hello, > > portmaster's feature to print collected pkg-message files after > successful installation is very useful. However, there are many ports > that echo messages from inside Makefile, usually in post-install phase > (but not exclusively there). > > A simple question: would it be possible (or better, would it be > desirable) to collect that text as well and to include it in the final > output in the same way it is done with pkg-messages? > Hi, It's better to correct these ports to make them use pkg-message, so it will be printed by portmaster *and* pkg_add (dont forget packages !) Best, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_debunk
On Thu, Dec 31, 2009 at 5:40 AM, Aleksandar Simic wrote: > Hello, > > I find that when building some ports, the building of its dependencies > tend to fail from time to time. > > So I've created pkg_debunk: http://github.com/dotemacs/pkg_debunk > > It shows you which ports that appear to be installed, aren't or if > they are for the most part, which of their content is missing. > > What do you think? > > Please note: I'm not subscribed to the list, so when replying do include me. > > Thanks, > Aleksandar Hi, What about `pkg_info -a -g` or `pkg_info -g pkgname` ? Regards, Julien ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: New version of the fakeroot patch
Hi porters, I do agree with the idea of a fakeroot. As bapt said, it will make supporting NOPORTDOCS easier: no more patches against the vendor Makefile(s) !!! It will also ensure the quality of the _packages_. For example, if the port create an empty folder, it's common that the package forget to create it. As the real installation is made with the pkg_add tool with this implementation, the porter will directly notice the issue. The major concern with this implementation is, IMHO, the intensive usage of I/O. But I'm sure we can reduce its impact on performance. To conclude, I think this patch is worth it. It'd be interesting to have the advice of a portmgr@ to know if it gonna break some obscure parts of the ports framework. Regards, Julien On Mon, Dec 14, 2009 at 7:13 AM, Baptiste Daroussin wrote: > Hi all, > > I have updated the fakeroot patch, it now can apply on an uptodate version of > the ports. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/133815 > > For information the fakeroot patch is a port of the midnightbsd's mports > fakeroot > to freebsd's ports. > > What it does: > - it is optional: you can activate it globally with USE_FAKE=yes in > /etc/make.conf or per ports by adding USE_FAKE=yes in the ports Makefile > > - it create a fakeroot directory in the WRKDIR where all the binary are > installed first > > - then it creates a package using the plist and finding its files only in the > fakeroot directory > > - in the end it installs the created packages > > - it respects the DESTDIR implementation (it is not the same kind of feature > nor > the same goal) > > - it does not require any modification on actual ports (except for those which > are already not clean) but will allow to cleanup some ports if wanted. > > Why this patch: > - it prevents installing crufts thing on users systems (only what is found in > the plist is really installed, so the package is always clean) > > I now that porters should take care of not breaking the plist, but it often > happens, helping them by a system that completly use the plist file is IMHO a > better thing, and it prevents users from being inpacted by a lazy porter. > > - it allow to create tinderbox that does not need to install a ports to get > the > package build, only build-depends ports will be installed > > - it allow easier handling of NOPORTDOCS, NOPORTEXAMPLES and so on, because it > creates the packages first using plist to know which files should be > packaged, > the porter should only take care of one case, the case everything is > installed, then he adapts the plists to have or not some files depending on > the options the user have. > > This should cleanup a lot some ports, and should easier the respectness of > some porting guidelines > > What could be done: > because it generates packages first we could imagine some lint programs that > analyse the package content to test that it respects some of the freebsd > recommandation for packages (usefull for porters), it could help the > validation > of new/update ports submission and help preventting commiting buggy stuff. > > Limitation: > this path (currently activable on depend) add from disk usage than the way > ports > actually works: > > without the patch: > build -> copy on the filesystem > with the path: > build -> copy-on-fakeroot->package_building->package-installing > > In the future it could be improved by provinding a version of pkg_create that > fake the package creation by directly install on FS so that could become > build->copy-on-fakeroot->package-installing > > This patch is not yet complete, it should work with classical ports that use > gmake or make and with python, I have only done that currenly as a proof of > concept. > > Tell me if you think that this patch could be interesting or not > > Regards, > Bapt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: adding users in ports
On Fri, Apr 3, 2009 at 2:40 PM, RW wrote: > On Fri, 3 Apr 2009 12:12:18 +0400 > subbsd wrote: > > >> My question - why do not make this facility by generic (for example >> create add/del/check-existence procedure in >> some /usr/ports/Mk/bsd.users.mk file) ? > > Presumably because the same functionality has to go into package files, > and work for someone that doesn't have a ports tree installed. That's where the staged installs are interesting. You implement the functionnality into the pkg_tools and the ports tree use them (make package before make install). It will also ensure that all post 'make package' features are supported by the pkg_tools because the ports tree will rely on that. An other solution, less elegant IMHO, is that the *.mk facilities generates the files/pkg-install.in file, which will be executed later by make or the pkg_tools. Well... that's *very* crappy :-) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
