Re: Explain staging
On Wed, Oct 02, 2013 at 10:44:32PM -0500, Stephen Montgomery-Smith wrote:
I have not been following discussions recently. There is this new thing
called staging. I don't seem able to find the original emails where
this was introduced.
Is there an email or a website which explains in some detail how staging
works? It is badly messing with a port I am developing. I can fix it
by setting NO_STAGE=yes, but I would like to get a better idea of why it
is failing. The failure is during the build process.
Sorry for not following closer.
Not a problem.
Staging is basically installing everything into a staging area ${WRKSRC}/stage
before messing up the system. What most of package system calls DESTDIR or
FAKEDIR.
From that stage a create can be directly created (even as a single user). or the
stage can be sync into the filesystem.
2 new targets can help you staging your ports: make check-orphans and make
makeplist.
You should have received 2 mails from me with some details about staging:
one called [HEADSUP] Stage support for the ports tree
and on called Staging, packages and more (very recent as of yesterday)
The following wiki page https://wiki.freebsd.org/ports/StageDir has been created
for tips and helps around staging.
Do not hesitate to add new entries to the wiki page, if you need any help
staging your ports I can provide reviews.
regards,
Bapt
pgpFGE_OUlO_d.pgp
Description: PGP signature
Re: Explain staging
From that stage a create can be directly created (even as a single user). or the stage can be sync into the filesystem. You probably meant to write: From that stage a *package* can be directly created ;) It's easy to understand why this is so useful because the result of the compilation does not have to be installed for real on the build host or build jail when the goal is just to create a package and clean up is lot easier. Keep up the good work, -Kimmo 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: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: You should have received 2 mails from me with some details about staging: one called [HEADSUP] Stage support for the ports tree and on called Staging, packages and more (very recent as of yesterday) I think the issue was that such very first email was lost somewhere, as Stefan said there isn't in the mailing list archive, I've never received originally, but there a few replies to it. Can you resend it to the list, please? - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlJNIK4ACgkQgRXp2M5fVU2alACeJOFyKCxkhx82fc792dIie7cN OMcAoOnn0HvdURdcD8ToW6i4RHROqyGJ =1icY -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
Re: Explain staging
Date: Thu, 3 Oct 2013 08:15:11 +0200
From: Baptiste Daroussin b...@freebsd.org
To: Stephen Montgomery-Smith step...@missouri.edu
Subject: Re: Explain staging
On Wed, Oct 02, 2013 at 10:44:32PM -0500, Stephen Montgomery-Smith wrote:
I have not been following discussions recently. There is this new thing
called staging. I don't seem able to find the original emails where
this was introduced.
=20
Is there an email or a website which explains in some detail how staging
works? It is badly messing with a port I am developing. I can fix it
by setting NO_STAGE=3Dyes, but I would like to get a better idea of why it
is failing. The failure is during the build process.
=20
Sorry for not following closer.
Not a problem.
Staging is basically installing everything into a staging area ${WRKSRC}/s=
tage
before messing up the system. What most of package system calls DESTDIR or
FAKEDIR.
sorry, I still don't get it.
What is achived by staging?
=46rom that stage a create can be directly created (even as a single user).=
or the
stage can be sync into the filesystem.
I don't understand what you mean.
Do you mean that an unprivileged user can
somehow install software from ports not under
/usr/local?
2 new targets can help you staging your ports: make check-orphans and make
makeplist.
You should have received 2 mails from me with some details about staging:
one called [HEADSUP] Stage support for the ports tree
and on called Staging, packages and more (very recent as of yesterday)
The following wiki page https://wiki.freebsd.org/ports/StageDir has been cr=
eated
for tips and helps around staging.
I've read your mails and the wiki page,
but still not sure what, if anything,
I need/could do with my ports.
I trust you know what you are doing,
but the meaning is not clear to me (yet).
Is the idea that all ports must/should
support staging?
If a port doesn't support staging,
will it fail portlint checks?
Thanks
Anton
___
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: Explain staging
On Thu, Oct 03, 2013 at 09:45:51AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: You should have received 2 mails from me with some details about staging: one called [HEADSUP] Stage support for the ports tree and on called Staging, packages and more (very recent as of yesterday) I think the issue was that such very first email was lost somewhere, as Stefan said there isn't in the mailing list archive, I've never received originally, but there a few replies to it. Can you resend it to the list, please? - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlJNIK4ACgkQgRXp2M5fVU2alACeJOFyKCxkhx82fc792dIie7cN OMcAoOnn0HvdURdcD8ToW6i4RHROqyGJ =1icY -END PGP SIGNATURE- Sure I will resend. I think I messed up somehow with my MUA while sending. regards, Bapt pgpiXnFkmtLpO.pgp Description: PGP signature
[HEADSUP] Staging, packaging and more
Hi all,
I want to give to all porters infomations on the rationnale behind all the
changes,
to explain why some things has happened, the rationale behind what we still need
to do to get the ports tree into a modern binary world.
1/ Staging
You may has notice that staging has hit the ports tree, staging is something
really important, all packages system are using that feature for eons, sometime
called DESTDIR sometime called FAKEDIR.
Staging is consistent in adding a new step while building packages: install
everything into ${STAGEDIR}. Then we can directly create packages out of that
directory without having to install into /. What the implementation does is:
With pkg_install (legacy package tools):
- Create a package from the stage directory
- Install that package.
With pkgng:
- Create a package from that stage directory
_OR_
- Install to / (pkgng can consider the stage directory as if it is a package)
What it means is, that it is the end of the bad plist, only things in plist are
really installed, this is the end of the broken packages that break the system
because they fail in the middle of make install as a package will only be
installed once we are sure the build process properly pass.
It allows right now to build and create a package without the need to be root.
It gives us new targets:
- make makeplist (to create the pkg-plist)
- make check-orphans (to print what is in the stage directory but not in
pkg-plist)
It reduces code duplication: in the end the installation is being done via a
package installation meaning that PKG-MESSAGE is automatically printed, all
pre/post installation scripts are executed.
It reduces patches: no need anymore to patch upstream Makefiles to avoid
installing the DOCS just do not list them in pkg-plist or conditionnaly list
them in the pkg-plist.
This also allows lots of new features to come:
- Allow to create sub-packages
- Allow to create debuginfo packages.
- Allow to do a lot of sanity check in the staging area to improve our QA
To convert your ports refer to: https://wiki.freebsd.org/ports/StageDir
Along with stage you have noticed that MAN* and MLINKS has gone, and now all the
manpages should be added to the plist. BTW MANCOMPRESSED is also not necessary
now.
There is 3 reason behind making it go and not being replaced:
- The initial goal of those macros was to be able to compress the right manpages
and to handle the different hardlinks/symlinks between those pages. Because it
was directly installed in / rather than using a stage directory, it was
necessary to at a point list them. and to properly track the different links
in MLINKS (which wasn't done properly in most ports btw :))
With stage, we have a new compress-man which does it properly on its own
without the need to get the list of the manpages, without the need of an
explicit declaration of the links.
This syntax to handle localized man pages was also terrific :)
and if you have a port mixing manpages in non regular and regular
localtion, it was totally messing
- Consistency, a port is basically: some metadata, a plist and some operations
to perform. for metadata all metadata are in the Makefile, all operations are
in the Makefile but plist can be a mix of pkg-plist and Makefile, this is
inconsistent, it makes sometime hard to figure out why a file has been added
to the plist etc.
Also this makes us having tons of targets define to handle those extras
entries and results in highly inefficient make(1) usage.
- stage is also a first step to go to sub-packages, sub-packages will basically
be: 1 port able to produce N packages, to be able to do this we will use
multiple plist, having the files properly defined already in plist will help
that. Having files defined in macros on Makefile will make it hard to
determine which one should go in which plist.
Last thing I would like to add about it: I don't see the difference personnaly
between listing N lines of manpages into Makefile MAN* macros where btw you have
to manually define the categories where to put them and adding those N lines
directly into the plist where make makeplist and/or make check-orphans can help
you getting the exact lines automatically?
2/ Binary packages
For the sake of being able to have clean working binary packages, pkgng has had
to use a dirty hack: origin is used has an identifier instead of the package
name.
Why: How to determine than ImageMagick-nox11 and ImageMagick are the same
package? and if I don't know they are the same package how to upgrade them
properly? same goes how the package manager can know that mysql-client-5.2.1 is
not an upgrade of mysql-client-5.0.1?
How can pkgng determine which subversion is the right version to use:
'pkg install subversion' will propose all possible subversion, in that case the
higher version is probably the default version, but in perl case, the higher
version is probably not the one you want.
Some packages are totally different project
Re: Explain staging
On Thu, Oct 03, 2013 at 09:45:51AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: You should have received 2 mails from me with some details about staging: one called [HEADSUP] Stage support for the ports tree and on called Staging, packages and more (very recent as of yesterday) I think the issue was that such very first email was lost somewhere, as Stefan said there isn't in the mailing list archive, I've never received originally, but there a few replies to it. Can you resend it to the list, please? Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html regards, Bapt pgp20DSGMMCum.pgp Description: PGP signature
Re: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlJNMdAACgkQgRXp2M5fVU11iQCgmj+i9/UUJDKP1mdgAzAMYbO2 MD8AnRbMZ3rQr+K9SSyXDFgPg1JsvHrc =KChF -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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/ocaml-lacaml | 7.0.7 | 7.0.10 +-+ www/xist| 3.25| 5.2.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org 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: Explain staging
On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. I mixed both in one :) regards, Bapt pgpc3Tr1PFVCi.pgp Description: PGP signature
Re: [HEADSUP] Staging, packaging and more
on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) All open up to a debate, of course. Thank you very much for doing this major step! - Allow to do a lot of sanity check in the staging area to improve our QA -- Andriy Gapon ___ 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
ports and NO_STAGE: portmaster leaves port-system in corrupt state
When NO_STAGE=yes is missing in the port's Makefile, as it is for a couple of ports like lang/perl5.16, then portmaster compiles, installs and - corrupt the port-system, because it tries to lstat files it can not find and ends up at the end of an unfinished installation. This leaves the entry in the installed-port database corrupted. The port got installed, but the database hasn't an entry anymore. I found that the port system is in a very bad shape when one is using CURRENT (10.0), where several things happened the same time like converters/libiconv ahs gone as required port, libstdc++ has gone in favour of libc++ and now ports that do not have this NO_STAGE= tag in the toplevel Makefile. About the last piece - I miss a warning/hint/information for those who has not the time following every second informations on the mailing lists! I regret that I forgot about three other ports I stumbled in where the missing NO_STAGE=yes obviously solved the problem after I put it into the Makefile - but that was simply a hunch - without knowing exactly what I do. Again, I miss some informations about that and googling didn't brought up deeper insight into that. If someone would be so kind an d delegate me to a proper official website where this NO_STAGE for the ports is explained a bit and further if someone tells me what to do when I stumble into the next port out of the 1200 I have to recompile, I would really appreciate that. Regards, O.H. signature.asc Description: PGP signature
Re: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 04:54 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. I mixed both in one :) I do appreciate the explanations very much. I am having a problem with a port in which if NO_STAGE is not set, then the build part of the process fails. As far as I can tell, staging should not effect the build part of the process in any way. So two questions: 1. If I set NO_STAGE=yes in that port, is this going to be a big problem? It will have to be a work around until I can get the next question answered: 2. Any ideas on why staging would effect the build process? The port includes subpackages that use ./configure; make; make install and are supposed to install into $WRKSRC/local, but instead sometimes installs into $WRKDIR/stage/portname/work/pkgname/local. Thanks, Stephen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSTWGBAAoJEC3xK9GaktgHbxUH+QFAGwLtosFLmskl0e/KB3qB zf+PP7UtZutAllfpFss/v1EgfioLOKq9jhggTeBRUClqj1enPcSeaNC4qEAOg4Zv oZeRGtPhV4kzUzvUhI0y6Odz1rANjQ1FiRZ0qrSNZXJqp+CLPItAHhiEKvesvUAm Ic3Z+jpG2XTZVNJIkZM8WUJjdCMNFjphRfyX4v3M4Q8+Q1CIETi+Re4ciiH/G3rX onuw5cTWR6PGymWfRLRTPaLNRftFXYMmDkhY/mMM3sg6vZVHdq6tSqpDa61qiuQx W4MsI6SaO/DEkorVcaesEWbNsgffNdN6fOJGCHHP4STcfVb3OE8r2rcpvs3XT3Y= =K3LU -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
Re: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 07:32 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 07:22:35AM -0500, Stephen Montgomery-Smith wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 04:54 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. I mixed both in one :) I do appreciate the explanations very much. I am having a problem with a port in which if NO_STAGE is not set, then the build part of the process fails. As far as I can tell, staging should not effect the build part of the process in any way. So two questions: 1. If I set NO_STAGE=yes in that port, is this going to be a big problem? It will have to be a work around until I can get the next question answered: 2. Any ideas on why staging would effect the build process? The port includes subpackages that use ./configure; make; make install and are supposed to install into $WRKSRC/local, but instead sometimes installs into $WRKDIR/stage/portname/work/pkgname/local. Thanks, Stephen Which port is that? Maybe I can help? It is math/sage. But I think it is working in this current port. The problem, I think, is in math/sage-devel, which exists only in my private ports tree. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSTWa5AAoJEC3xK9GaktgHM1AIAMZcwUMiD5tUU+qsM+ruKXLd +6RMANAhiwfGqpkW80FsplgO8siZ9eh8JZuCOYyymO51NkX4L59GBqsDT7DjgXS2 zcZjK/ClxTyj2iZI+zxTXoc8RO0mZuKkOcsOWNsOuEO3X0YpPAGCl98iGWf+/knX HN/ez862Tx8Oee28BTfZzX0vaHVLQotPyDfV+DPgUfMCQIfztotqlsJcKAfdwENk Y6W5lbZwCYdhWswn5cFfsLJ92EfEbBJnGS9tTBq1GXZzuKlsq3gcfc27UoJoc5zj GVUuiW4+kDVeVluta1b0xNLi9Q+/7nQF9fF+hed7PwssbHNNj9sFH5ZtLEylWNM= =l71P -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
Re: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 07:44 AM, Stephen Montgomery-Smith wrote: On 10/03/2013 07:32 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 07:22:35AM -0500, Stephen Montgomery-Smith wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 04:54 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. I mixed both in one :) I do appreciate the explanations very much. I am having a problem with a port in which if NO_STAGE is not set, then the build part of the process fails. As far as I can tell, staging should not effect the build part of the process in any way. So two questions: 1. If I set NO_STAGE=yes in that port, is this going to be a big problem? It will have to be a work around until I can get the next question answered: 2. Any ideas on why staging would effect the build process? The port includes subpackages that use ./configure; make; make install and are supposed to install into $WRKSRC/local, but instead sometimes installs into $WRKDIR/stage/portname/work/pkgname/local. Thanks, Stephen Which port is that? Maybe I can help? It is math/sage. But I think it is working in this current port. The problem, I think, is in math/sage-devel, which exists only in my private ports tree. Also, I am not in a super hurry to fix this problem. Work and family life are quite big stressors in my life right now. Fixing easy bugs and updates to the ports is quite relaxing, but something that will require a full investigation like this is going to be on a waiting list. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSTWk5AAoJEC3xK9GaktgHoT0IAJN0Sn6rBCBetZqa2FuM/EPm GNe4diIX/cs0UKYZZQN9Gj8g5EXNgNaDJ1nPuTHt4jAyo92YYM6GTLSsPBhfY7rA D6cfmYMUEVY2YtKODigjMb7XF6F9Lv6hZkNnuiZGUwAmW0FmDCejysP0M+qlmHEf xgLLhzCJ1w64vbgr7/OzMdb4FftR/ja1F5UFJjwGZakVcSQEhRL0N4kdEzTC0/PT My85TEvyUg0N1QrcZRrvLfcZFkpSeqjPscRo+LptvVSFf2PtkTZOOtArYbFIattY +oCn/G301YLawG78lRrnLYxuCxYVHwzZSalMTzcc5c61Hdvf2ooCUBokI5MoAfc= =qgOF -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
Re: Chromium and HEAD
On Wed, 2 Oct 2013 22:10:24 -0400 Sam Fourman Jr. sfour...@gmail.com wrote: using a recent FreeBSD amd64 FreeBSD NewBSD 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #0 r255942: Sun Sep 29 20:05:41 UTC 2013 I am running chromium built with default options(clang33 from ports) when you use the address bar to search, chromium will coredump if the first letter you type is the letter a is anyone else seeing this? Nope, but I built it with gcc on September 14th, so it's not the latest version. -- Gary Jennejohn ___ 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
new DEFAULT_VERSIONS variable
I just saw this in UPDATING: 20131003: AFFECTS: users of lang/python* and ports AUTHOR: m...@freebsd.org The default versions of lang/python* have been changed to support the new DEFAULT_VERSIONS variable. PYTHON_DEFAULT_VERSION, PYTHON2_DEFAULT_VERSION and PYTHON3_DEFAULT_VERSION are deprecated. If you have set them in your make.conf, you should change them something like DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.3 Does this affect BERKLEY DB or Ruby also? If not, is it a planned future implementation? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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 DEFAULT_VERSIONS variable
On Thu, Oct 03, 2013 at 09:47:43AM -0400, Jerry wrote: I just saw this in UPDATING: 20131003: AFFECTS: users of lang/python* and ports AUTHOR: m...@freebsd.org The default versions of lang/python* have been changed to support the new DEFAULT_VERSIONS variable. PYTHON_DEFAULT_VERSION, PYTHON2_DEFAULT_VERSION and PYTHON3_DEFAULT_VERSION are deprecated. If you have set them in your make.conf, you should change them something like DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.3 Does this affect BERKLEY DB or Ruby also? If not, is it a planned future implementation? The entry as of 20130920 stated also perl5, ruby, tcltk. I would be glad to see bdb, postgresql, mysql, etc also being added here :) regards, Bapt pgpwMIoCtBUVz.pgp Description: PGP signature
Re: Chromium and HEAD
On Wed, Oct 02, 2013 at 10:10:24PM -0400, Sam Fourman Jr. wrote: using a recent FreeBSD amd64 FreeBSD NewBSD 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #0 r255942: Sun Sep 29 20:05:41 UTC 2013 I am running chromium built with default options(clang33 from ports) when you use the address bar to search, chromium will coredump if the first letter you type is the letter a is anyone else seeing this? Same for me using the version from pkg-test. pgpLcCUGdOoxC.pgp Description: PGP signature
graphics/ocropus fails to build on 9.2-R ports rev 329191
Hello freebsd-ports,
# svn info /usr/ports
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: https://svn0.eu.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn0.eu.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 329191
Node Kind: directory
Schedule: normal
Last Changed Author: bf
Last Changed Rev: 329191
Last Changed Date: 2013-10-03 14:47:44 +0100 (Thu, 03 Oct 2013)
graphics/ocropus fails to build and gives the following error:
=== Building for ocropus-0.4_11
Making all in .
gmake[1]: Entering directory
/usr/ports/graphics/ocropus/work/ocropus-0.4/ocropus'
clang++ -DPACKAGE_NAME=\ocropus\ -DPACKAGE_TARNAME=\ocropus\
-DPACKAGE_VERSION=\0.3\ -DPACKAGE_STRING=\ocropus\ 0.3\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\ocropus\
-DVERSION=\0.3\ -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DHAVE_FLOAT_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1 -DHAVE_LIBZ=1 -DHAVE_LIBPNG=1
-DHAVE_LIBJPEG=1 -DHAVE_LIBTIFF=1 -DHAVE_LIBPTHREAD=1
-DHAVE_LIBIULIB=1 -DHAVE_LIBLEPT=1 -DHAVE_LIBGSLCBLAS=1
-DHAVE_LIBGSL=1 -DHAVE_LIBGOMP=1 -DHAVE_FORK=1 -DHAVE_VFORK=1
-DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -DHAVE_DUP2=1
-DHAVE_MEMSET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRDUP=1
-DHAVE_STRRCHR=1 -I. -I./include -I./ocr-utils -I/usr/local/include
-I/usr/local/include/leptonica -DHAVE_LEPTONICA -I/usr/local/include
-O2 -pipe -fstack-protector -fno-strict-aliasing -fopenmp -Wall
-Wno-sign-compare -Wno-write-strings -Wno-deprecated -O2 -pipe
-fstack-protector -fno-strict-aliasing -fopenmp -MT didegrade.o -MD
-MP -MF .deps/didegrade.Tpo -c -o didegrade.o test -f
'./ocr-utils/didegrade.cc' || echo './'./ocr-utils/didegrade.cc
clang++: warning: argument unused during compilation: '-fopenmp'
clang++: warning: argument unused during compilation: '-fopenmp'
In file included from ./ocr-utils/didegrade.cc:25:
In file included from /usr/local/include/iulib/imglib.h:29:
In file included from /usr/local/include/iulib/imgfilters.h:30:
In file included from /usr/local/include/colib/colib.h:34:
In file included from /usr/local/include/colib/classifier.h:33:
/usr/local/include/colib/narray.h:79:5: warning: 'narray' defined as a
class template here but previously declared as a
struct template [-Wmismatched-tags]
class narray {
^
/usr/local/include/colib/narray.h:66:5: note: did you
mean class here?
struct narray;
^~
class
In file included from ./ocr-utils/didegrade.cc:25:
In file included from /usr/local/include/iulib/imglib.h:29:
In file included from /usr/local/include/iulib/imgfilters.h:30:
In file included from /usr/local/include/colib/colib.h:37:
/usr/local/include/colib/env.h:36:17: warning: using
directive refers to implicitly-defined namespace 'std'
using namespace std;
^
In file included from ./ocr-utils/didegrade.cc:26:
In file included from ./ocr-utils/didegrade.h:29:
In file included from ./include/ocropus.h:61:
./ocr-utils/enumerator.h:83:25: error: call to
function 'Hash_hash' that is neither visible in the template
definition nor
found by argument-dependent lookup
int index = abs(Hash_hash(key)) % entries.length();
^
./ocr-utils/enumerator.h:71:21:
note: in instantiation of member function 'EnumHashint,
int::find_index' requested here
int index = find_index(key);
^
./ocr-utils/enumerator.h:116:34: note: in
instantiation of member function 'EnumHashint, int::get' requested
here
int result = translation.get(i,n);
^
./ocr-utils/enumerator.h:105:12:
note: 'Hash_hash' should be declared prior to the call site
inline int Hash_hash(int x) {
^
2 warnings and 1 error generated.
gmake[1]: *** [didegrade.o] Error 1
gmake[1]: Leaving directory
/usr/ports/graphics/ocropus/work/ocropus-0.4/ocropus'
gmake: *** [all-recursive] Error 1
*** [do-build] Error code 1
Stop in /usr/ports/graphics/ocropus.
*** [build] Error code 1
Stop in /usr/ports/graphics/ocropus.
can anyone help?
thanks,
--
John
___
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] Staging, packaging and more
On Thu, Oct 03, 2013 at 09:50:22AM -0700, Kevin Oberman wrote: On Thu, Oct 3, 2013 at 5:17 AM, Andriy Gapon a...@freebsd.org wrote: on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) All open up to a debate, of course. Thank you very much for doing this major step! -- Andriy Gapon Staging is a major step forward and I am very happy to see it. This very well written message on not only what staging is, but why it is important is going to make a lot of people comfortable about what has happened, but I really wish this message had come out before it was introduced into ports. That would have eliminated a lot of confusion as to what was going on. There have been a LOT of major changes to ports/packages over the past few months and I really, really appreciate all of the work put into them, but I would be even happier if there was a bit more communication about what is changing just to avoid confusion. Thanks again for the work on this and other recent ports/pkg updates. I messed up with my MUA, and this message only went to some private mailing list while it was supposed to be sent to a couple of public mailing list, that is the reason why you haven't seen it before. Sorry about that. regards, Bapt pgpXKhLK0Qkg9.pgp Description: PGP signature
Re: [HEADSUP] Staging, packaging and more
On Thu, Oct 3, 2013 at 5:17 AM, Andriy Gapon a...@freebsd.org wrote: on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) All open up to a debate, of course. Thank you very much for doing this major step! -- Andriy Gapon Staging is a major step forward and I am very happy to see it. This very well written message on not only what staging is, but why it is important is going to make a lot of people comfortable about what has happened, but I really wish this message had come out before it was introduced into ports. That would have eliminated a lot of confusion as to what was going on. There have been a LOT of major changes to ports/packages over the past few months and I really, really appreciate all of the work put into them, but I would be even happier if there was a bit more communication about what is changing just to avoid confusion. Thanks again for the work on this and other recent ports/pkg updates. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com ___ 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
can't build xorg FreeBSD-9.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, i have problems to build xorg-7.7 and xorg-apps-7.7 using clang. xrandr: /usr/local/lib/libXrandr.so: undefined reference to `_XEatDataWords' /usr/local/lib/libXrandr.so: undefined reference to `_XGetRequest' xdpyinfo: /usr/local/lib/libXcomposite.so: undefined reference to `_XGetRequest' xinput: checking for XI2... yes checking for XI21... no configure: error: Package requirements (xi = 1.4.99.1 inputproto = 2.0.99.1) were not met: Package dependency requirement 'xi = 1.4.99.1' could not be satisfied. Package 'xi' has version '1.4.5', required version is '= 1.4.99.1' xev: /usr/local/lib/libXrandr.so: undefined reference to `_XEatDataWords' /usr/local/lib/libXrandr.so: undefined reference to `_XGetRequest' xvinfo: /usr/local/lib/libXv.so: undefined reference to `_XEatDataWords' /usr/local/lib/libXv.so: undefined reference to `_XGetRequest' here my make.conf: CC= clang CPP=clang-cpp CXX=clang++ #WITHOUT_CLANG=YES WITH_NEW_XORG=YES WITHOUT_KOFFICE=YES WITH_CUPS=YES NO_LPR=YES LOCALIZED_LANG=de_DE WITH_KDE4=YES WITHOUT_GNOMEVFS=YES CUPS_OVERRIDE_BASE=YES OVERRIDE_LINUX_BASE_PORT=f10 OVERRIDE_LINUX_NONBASE_PORTS=f10 WITH_SYSTEM_CLANG=YES #MAKE_JOBS_UNSAFE=yes WITH_PKGNG=YES can anybody help me? Thanks. Suri -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJSTamNAAoJEDyDkpKh+9pTh3MP/2u+jsJywrxFr6OBhZVrle3W OCbK39y75Zq2ykYrjURoUIfBIcV25Sfyoe2/Lv3ajqTefkSnmC4qWcFV4GJxfPLA 6Z6P6pOjm2rGONEfQX9GrJR5RmT53OAjB3gbERnFboS4+ggPpWwHSabP2hXDzlR2 lZ1dR6PVD4Uym66OhyC4SEFX28SOdExtZu12sRJg3S71p/MzIzSU+TzJS6kVVg8V Smq/X0fJFAvJsAhuGBw7Pp/2nomsmzNSapj8PYQS8kM+XxDCduo2kBOVnCiD47PF eaVds03ciVi59DuRCbN8VraE2OufrH0nYUlyNeRo2enXWT2owrPoLBFd90FNOUP5 zQzGbYAAlbuDsPifP1GYY0tsGm/NuTI05DwWL/OJxAKbmCHVSMhPoVc4HLipCigG aOvsO5Lq6DoIqSIWJHAjYplkLQSj2OTAFL28unhq+jYl7r5pVvHcEanQbTJTa3gx Tzyok9g/Q/HF1ARGMqK9s8i0SRo1jckURFM43dUgPc1zON01rGta14dQHPCH3CVj 1hkrpNniLH2+/Rtyy3SgQDsVbfXLr3ndR3KFZUgY/K2U1Fk9C4bClUnwAR8z5PhF AMp2pUV5sAcHNAXqzdCv8/WvPKPqwvP75CY7mUaPGupXXne9NiI0det+y6xLYNVn UGpjzUVBJOFxNhd4WqsB =RIws -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
ports/182357: Delete mail/squirrelmail-postfixadmin-plugin port
Would someone commit this please? 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
FreeBSD Port: unixODBC-2.3.1
Bonjour, How to get free UNIXodbc for Firebird in Mac OS X 10.8.5 ? 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
Re: [HEADSUP] Staging, packaging and more
Hi, I have question do we really need to build *doc packages every time or we can download prebuilded documentation for stable ports? There's two versions of documentation distributed separately for most ports: doc-source and doc-builded. And there's very few situations when we really need build documentation from scratch. Otherwise we can download prepackaged versions from distribution site. For example, I don't need TeX or docbook distribution on my server to read the documentation I can download directly if I don't really want to build it. On Thursday, October 3, 2013, Andriy Gapon wrote: on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) All open up to a debate, of course. Thank you very much for doing this major step! - Allow to do a lot of sanity check in the staging area to improve our QA -- Andriy Gapon ___ freebsd-ports@freebsd.org javascript:; mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.orgjavascript:; -- -- Eir Nym ___ 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] Staging, packaging and more
On, Thu Oct 03, 2013, Nathan Whitehorn wrote: On 10/03/13 07:17, Andriy Gapon wrote: on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) Please no devel packages. Seconded. Cheers Marcus pgpMsSPQ2iAq5.pgp Description: PGP signature
Re: Explain staging
On 03/10/2013 08:56, Anton Shterenlikht wrote:
sorry, I still don't get it.
What is achived by staging?
There are 4 main advantages:
1) You can build a port and then create a package from the stage
directory without having to install it on your build system. You
usually don't need root privileges to do this.
This actually makes it a lot easier to eg. build ports away from your
frontline servers and then quickly install them from packages, thus
minimizing disruption to live services.
2) Instead of (typically) just running the install target of the
piece of software, and then trusting that the pkg-plist contains
an accurate list of what gets installed, now we take the pkg-plist
and extract the matching items from the stage directory to make a
package. Only things on the plist get installed, and things on
the plist but not present in the staging dir will flag up as an
error in the port.
ie. leftovers or other unrecorded files cluttering up your system are
now a thing of the past. Because there's only one port installed into
the staging dir, there's no ambiguity about which file belongs to which
package.
This also enables the potential for a future enhancement: creating
several different packages from one stage directory. In the simplest
case, this would mean being able to create a separate package for the
docs or examples, so you could avoid having to install that stuff if
using binary packages. Beyond that, there could be separate packages
for eg. the shared libraries from a package. So, for something like
mysql-client: at the moment, mysql-client packages for different
versions of mysql conflict. Having separate mysql-shlibs packages for
different versions of mysql should not suffer from such conflicts.
3) Because there's just the result of building one port in the
staging directory, it makes it much easier to run various
heuristics and quality assurance tests against the build results
without getting mixed up with files from other packages.
There are a lot of fairly dodgy ports in the tree which have bit-rotted
over time or suffered from lack of active maintainership. There are a
pretty large number that haven't adopted what is considered the best
current practice for such things as eg. USES flags.
4) Instead of having to have duplicate methods of doing post install
actions -- eg. displaying a pkg-message -- between installing
from a port vs. installing from a package, now you only need to
write the actions for installing via a package. This simplifies
many port makefiles considerably.
Getting rid of this duplication of effort is going to improve port
quality a great deal. Previously it was the case that code for doing
post-install actions when installing from a package was not tested
really at all. Much of that code has been broken in the ports for quite
some time.
There are numerous other advantages that should accrue evenually. For
instance, converting many port options into separate sub packages. But
that's all in the future.
I don't understand what you mean.
Do you mean that an unprivileged user can
somehow install software from ports not under
/usr/local?
No. It means you can create a package tarball foobar-9.9.99.txz as a
non-root user. You cannot then take that package and install it into
${LOCALBASE} without root level privileges.
I've read your mails and the wiki page,
but still not sure what, if anything,
I need/could do with my ports.
Basically:
If you have an instruction in you port to install a file from the build
area into the filesystem under ${PREFIX} = /usr/local then you need to
change it to install to ${STAGEDIR}${PREFIX}/whatever. Note: this only
applies to the *install* parts: when building the package, you should
configure it for the eventual final install location under /usr/local.
(It's quite a lot like using DESTDIR to install the base system into a
jail. Once you're in the jail, everything appears in it's proper place,
but from outside that's not the case.)
Where you don't have explicit install lines in you port, instead relying
on an install target from the package itself, usually that will be
handled automatically and you won't need to do anything.
If you have any post-install actions, where those are duplicated by eg.
pkg-install scripts, then you can just delete them from the port's
Makefile. Otherwise you'll need to convert the post-install actions to
a pkg-install script, or otherwise enable them to happen at package
install time.
Is the idea that all ports must/should
support staging?
Yes.
If a port doesn't support staging,
will it fail portlint checks?
There's a 6 month target to convert the entire ports tree to staging.
Any ports not converted to use staging after that will be considered to
be broken. If no one steps up to fix them, then after a suitable period
of deprecation they may well end up being removed.
No
Re: [HEADSUP] Staging, packaging and more
El 03/10/2013 22:41, Marcus von Appen m...@freebsd.org escribió: On, Thu Oct 03, 2013, Nathan Whitehorn wrote: On 10/03/13 07:17, Andriy Gapon wrote: on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) Please no devel packages. Seconded. What's wrong with devel packages? Cheers Marcus ___ 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: Explain staging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 07:22 AM, Stephen Montgomery-Smith wrote: On 10/03/2013 04:54 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. I mixed both in one :) I do appreciate the explanations very much. I am having a problem with a port in which if NO_STAGE is not set, then the build part of the process fails. As far as I can tell, staging should not effect the build part of the process in any way. So two questions: 1. If I set NO_STAGE=yes in that port, is this going to be a big problem? It will have to be a work around until I can get the next question answered: 2. Any ideas on why staging would effect the build process? The port includes subpackages that use ./configure; make; make install and are supposed to install into $WRKSRC/local, but instead sometimes installs into $WRKDIR/stage/portname/work/pkgname/local. FYI So when NO_STAGE is not set, MAKE_ARGS includes DESTDIR=$WRKDIR/work/stage. This messes up the build process on this port. This is probably something to be fixed way down the road, and perhaps it is my port that needs fixing. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSThgPAAoJEC3xK9GaktgHHDEIALDlt86BrDvR2CjjINGwyQdh okMhRAM0my/XftIy+2GHMAh95+l86LW4cDDpgLFneydjWLwRV3ZQBb4H6up0MpWN +MrNeruNirl17XdoRcOEXyBHbtbbym1bIToAGuPOvJGocvOoer9HKpYxZ3sX/OCU uL+nr/Zh7pdJq0TgwCXlhNTQnf77qZEnQcrYxjEpBP+zgQz7gXpH+RfC0yfbXERP zeOEEojdy7Y6IZyzd9C+TskEn5VH1DH0MSz9/sOVzRgebh51SRWMFWtCgPiNJZBE 04A96X/RiY1boKK1QK3/hjlLqDlVY8UPLTvGtvaUolJPGHDLR1oJfyKYxUw33oU= =RCk8 -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
Re: Explain staging
On Thu, Oct 03, 2013 at 08:21:19PM -0500, Stephen Montgomery-Smith wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2013 07:22 AM, Stephen Montgomery-Smith wrote: On 10/03/2013 04:54 AM, Baptiste Daroussin wrote: On Thu, Oct 03, 2013 at 10:58:56AM +0200, Alex Dupre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baptiste Daroussin ha scritto: Here you are: http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html I was referring the the previous one: [HEADSUP] Stage support for the ports tree. Dunno if it had additional info or this second one is enough. I mixed both in one :) I do appreciate the explanations very much. I am having a problem with a port in which if NO_STAGE is not set, then the build part of the process fails. As far as I can tell, staging should not effect the build part of the process in any way. So two questions: 1. If I set NO_STAGE=yes in that port, is this going to be a big problem? It will have to be a work around until I can get the next question answered: 2. Any ideas on why staging would effect the build process? The port includes subpackages that use ./configure; make; make install and are supposed to install into $WRKSRC/local, but instead sometimes installs into $WRKDIR/stage/portname/work/pkgname/local. FYI So when NO_STAGE is not set, MAKE_ARGS includes DESTDIR=$WRKDIR/work/stage. This messes up the build process on this port. This is probably something to be fixed way down the road, and perhaps it is my port that needs fixing. If for your port DESTDIR means something else, and STAGEDIR is expecting to be exposed though another variable then change DESTDIRNAME which is DESTDIR by default. regards, Bapt pgpxYy9mirfni.pgp Description: PGP signature
