Date: Sun, 06 Mar 2011 19:37:24 +0100 From: Grzegorz Blach <magik@roorback.net> To: bf1783@gmail.com Cc: "b. f." <bf1783@googlemail.com>, freebsd-ports@FreeBSD.org Subject: Re: FreeBSD needs fresh Blood! Message-ID: <4D73D464.3070806@roorback.net> In-Reply-To: <AANLkTi=d5hP-WHPQVJYk9%2B7gXd-3d5j_wgypz7QM2A6X@mail.gmail.com> References: <AANLkTi=d5hP-WHPQVJYk9%2B7gXd-3d5j_wgypz7QM2A6X@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/06/2011 18:35, b. f. wrote: >> I read last post Martin Wilke's blog called "FreeBSD needs fresh Blood!" >> >> First of all, I think it's difficult to testing ports. >> >> I'm using testing release of VirtualBox, >> but for build this port I must download patches, >> apply its on my own tree and merge its with official ports >> using portshaker. >> >> It's possible to build testing ports outside tree, >> but I must build every port separately, since `Make` don't known how to >> track dependencies. > > There is always going to be some added work involved in testing. Have > you considered using multiple trees, if you have sufficient disk > space? Or using a version control system? > Multiple trees don't help me a lot, portmaster became fools. There is no significant difference if I use version control system or portshaker to merge trees. >> >> Another possibility is replace ports in disk, but after upgrade tree eg. >> with portsnap I lose my changes, and portmaster want to rebuild these >> ports to stable release. >> > > It sounds like you are using the wrong tools. Although portsnap (which > is not best suited for this purpose) has path arguments and an -l flag > that can be used to add or preserve local changes, and both portmaster > and portupgrade have options to ignore certain ports or to substitute > alternative dependencies, you shouldn't have to make use of them. > Instead, you should probably be using CVS (or another version control > system that can import CVS), which will make merging and reverting > changes easier. And naturally you shouldn't run updating tools until > you've modified your tree. But I won't resign from use updating tools, even when I use merged tree. Because I use merged tree all the time. >> If testing will be simpler, I think more people will do this. >> Maybe we must create two trees, eg: ports-stable and ports-current >> First we publish changes to current tree and after week or two without >> pr, we publish updates to stable tree too. > > This has often been proposed, but since it would require more work > from the already-overstretched committers, and the benefits are > questionable, I don't think it is likely to happen soon. > >> >> Merging trees is another huge problem. >> Portshaker do this very well, but after merge I must rebuild INDEX file, >> which takes long time. This should be faster or even shouldn't be >> required (hard to do). > > Do you really need to rebuild the INDEX? You can often avoid using > it. If you do need to modify it, you can use some improved method, > like > > http://www.lpthe.jussieu.fr/~talon/build_index.py > > or modify it incrementally, with something like > ports-mgmt/p5-FreeBSD-Portindex, > > http://www.lpthe.jussieu.fr/~talon/portindex-18_1.tgz > > , or your own script. > > b. I known that are many different ways to merge ports from different sources, but none of them are simple and fast to use it for first time. Look at last calls for testers: http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/065884.html http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/065983.html There are only links to tarballs, without address to repository. I must download tarballs, commit ports to my tree and merge it with official ports. Another CFT: http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/066007.html There is address for repository, but I still need merging trees and rebuild index for portmaster. I thing if testing ports will be simpler, more people can do this, and want to do this. I proposed stable and current trees, but maybe one official merge tool, which is easy to setup will be better, or something completely different. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNc9RkAAoJEFCzIDMxqoILknMH/2ewFVhIWz02xCXFzp7vNtPO wkcJmzIUjF9LxKQ1mTdsZbBboIWzchihLZoCa8GDhZYmFgGnzhl7UDeDzjJ4/+fL DKcAkmixOR2TbFKoZf8C52wIv4bE9WuuuUlibVyctK4/3rXB3NOpq4xXi1dT5G3q ZzdpWdBi3p6Ec9bnRuWl/aqMhIbHq9NweX50pB4TF5Wldv3fWAGGL/kLOHnAEzCr 8vVRRz6QfnKbrxY830fs5wodgRJGCEWzfat33Y0jV5UWKQwW01f2CxRm9tzbuIJJ X/Nr0QLdi0L7OXEpqaak4OCIUl1M3UCKM2lYovlRt5lXb/0PrAdeZzgzHWMNH9s= =Kl87 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D73D464.3070806>