Re: x11/hs-x11-ghc can't find proper version of haddock
Hello Josh, On Tue, May 19, 2009 at 11:32 PM, Josh Rickmar wrote: > I am trying to install xmonad, but the hs-x11-ghc dependency is not > building. It is looking for a haddock version >=0.6, but can not find > what the version actually is. I am on it :) Hopefully, I can tell you what the problem is soon. Cheers, :g ___ 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 portmgr secretary: Thomas Abthorpe
On Thu, Mar 18, 2010 at 5:02 PM, Erwin Lansing wrote: > On behalf of portmgr, I am pleased to announce that portmgr has found > a new secretary: Thomas Abthorpe. [..] > Please welcome him onboard! Welcome! :g ___ 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: Compiling for i386 on amd64 using tinderbox
Hej, On Wed, Apr 21, 2010 at 1:07 PM, Christopher Key wrote: > patch uname to return the appropriate answer I do not think you will need this since answers returned by uname(1) can be customized easily, just check its manual page to see how to do that. Cheers, :g ___ 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: Compiling for i386 on amd64 using tinderbox
On Wed, Apr 21, 2010 at 3:13 PM, Christopher Key wrote: > Setting ARCH, UNAME_m and UNAME_n [..] did the trick. I wonder if tinderbox > should instead be setting these values automatically [..] Ask/request it on the Tinderbox mailing list :) :g ___ 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: [ HEADS UP ] Ports unstable for the next 10 days
On Wed, Apr 21, 2010 at 10:52 PM, Chip Camden wrote: > lang/ghc is still marked IGNORE, unless I'm missing something. Yes, if your system is older than 6.0 on i386 and older then 7.0 on amd64, it is still ignored, since we do not support those platforms. Otherwise it must be okay. Cheers, g. ___ 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: FreeBSD Port: xmonad-0.9.1_1
On 04/30/10 19:39, Giuseppe Pagnoni wrote: > xmonad crashes on startup with the following error message: > > /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required > by xmonad -x86_64-freebsd [..] > the xmonad dependency on libgmp was not updated in the port's files > to follow the recent libgmp bump. It was updated, just check it out at the right place [1]. On 04/30/10 20:29, freebsd-po...@coreland.ath.cx wrote: > This might have something to do with the way that xmonad recompiles > itself and saves a copy of the binary in your $HOME. Have a look in > ~/.xmonad, I think... Yes, that makes sense I think. What happens if you simply remove the xmonad binary in ~/.xmonad? Cheers, :g [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/xmonad/Makefile.diff?r1=1.14;r2=1.15 ___ 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: FreeBSD Port: xmonad-0.9.1_1
On Mon, May 3, 2010 at 11:01 AM, Giuseppe Pagnoni wrote: > Yep, that was exactly the problem. Removing the executable in > ~/.xmonad makes xmonad start up correctly now. Meanwhile I found that the same effect can be achieved by issuing `xmonad --recompile`. I think it is always needed on each shared library bump. Cheers, :g ___ 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"
Renamed Haskell Applications
Hello there, Recently I have tagged the following popular but Cabalized applications in the Ports Collection with the "hs-" prefix: - darcs [1]: devel/darcs -> devel/hs-darcs - pandoc [2]: textproc/pandoc -> textproc/hs-pandoc - xmonad [3]: x11-wm/xmonad -> x11-wm/hs-xmonad, x11-wm/xmonad-contrib -> x11-wm/hs-xmonad-contrib - xmobar [4]: x11/xmobar -> x11/hs-xmobar I would like to ask everybody who is reading this message and using any of these ports to comment on this change. The reason was to do so that they are direct translation of their hackages coming HackageDB [5], and as the port of the Haskell Platform [6] is under way they would really serve the purpose for representing the FreeBSD (binary and stable) version of the corresponding applications. So there would be two (mutually exclusive) ways for installing them. In case of xmonad: - The native way: # pkg_add -r haskell-platform # cabal install xmonad Pros: Access updates and fixes immediately, not need for using the Ports Collection, support for multiple versions for the same packages. Cons: Need to build everything from sources, packages might be broken, cannot remove installed applications. - The FreeBSD way: # pkg_add -r hs-xmonad Pros: Reliable and stable dependencies, versions and updates, support for binary-only installs, support for removing packages. Cons: Might not be the up-to-date, multiple versions for the same package are not supported, not every package is ported. Please send "+1" or "-1" depending on whether you support or object this change. Thank you! Cheers, :g [1] http://www.darcs.net/ [2] http://johnmacfarlane.net/pandoc/ [3] http://www.xmonad.org/ [4] http://code.haskell.org/~arossato/xmobar/ [5] http://hackage.haskell.org/ [6] http://hackage.haskell.org/platform/ ___ 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 looking for maintainer
On 06/09/10 18:13, Gabor Kovesdan wrote: >> >>> Why don't you so it yourself now that you can? :) Talk with your mentor about this. >>> Not until my account gets created. But thanks for reminding :) >>> >> >> Ok, I'll do. Which is your account name that is being created? >> > Well, I mean it would be practical to assign them directly to your > @FreeBSD.org address but now I'm just thinking that the alias is not > working yet, so maybe it's better to wait until you get it and then > you can do it yourself also. > I think his normal email address will do for now, then he can change it to his @freebsd.org address later on. Cheers, :g ___ 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: x11/stumpwm and ports/149397
Hello, On Sat, Sep 4, 2010 at 8:00 PM, Anonymous wrote: > Since the PR was handed over to you by p...@[1] I haven't seen any activity > for around a month. Do you even have an interest in the lisp port? It was assigned to jacula@ for mentoring purposes, i.e. to learn work with PRs. It is possible that he could not spend enough time on the PRs I gave him to work with. I am re-assigning your PR to my another mentee, ashish@, and he will take care of it soon. Sorry for the inconveniences. :g P.S.: It was not mistaken for a Haskell port :) ___ 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: [Haskell] Announce: The Haskell Platform 2011.4
Hello there, On Sat, Dec 17, 2011 at 10:04 PM, Don Stewart wrote: > We're pleased to announce the release of the Haskell Platform: a > single, standard Haskell distribution for everyone. > > Download the Haskell Platform 2011.4.0.0: > > http://haskell.org/platform/ > > The specification, along with installers (including Windows, Apple and > Unix installers for a full Haskell environment) are available. > > The Haskell Platform is a single, standard Haskell distribution for > every system, in the form of a blessed library and tool suite for > Haskell distilled from the thousands of libraries on Hackage, along with > installers for a wide variety of systems. It saves developers work > picking and choosing the best Haskell libraries and tools to use for a > task. > > When you install the Haskell Platform, you get the latest stable > compiler, an expanded set of core libraries, additional development > tools, and cabal-install – so you can download anything else you need > from Hackage. > > What you get is specified here: > > http://hackage.haskell.org/platform/contents.html For your information, it is available for FreeBSD as well. Though note that the corresponding ports can be only found at our GitHub repository for now: https://github.com/freebsd-haskell/freebsd-haskell/ In order to use the ports from this repository, you will have to install and configure portshaker(8). For further details, see the README file in the repository. After merging the ports trees, Haskell Platform can be installed by the following command: # cd /usr/ports/devel/hs-haskell-platform/ && make install clean or updated in the conventional way, e.g. by portmaster(8) (together with other Haskell ports): # portmaster -r ghc They are published this way, because the FreeBSD Ports Collection is only partially thawed (large-scale changes, like updating core Haskell packages or GHC, are still not allowed) due to the on-going release cycle for FreeBSD 9.0. On behalf of the FreeBSD Haskell Team, Gabor ___ 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: incorrect format for some MOVED entries from 2011-05-08
On 05/09/11 08:33, Andriy Gapon wrote: > The empty field for a new port name seems to be missing here. Yes, it is correct; it was my mistake. It has been fixed by now. Thank you for reporting 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: Fwd: INDEX build failed for 7.x
On 05/10/11 02:44, Erwin Lansing wrote: >> INDEX build failed with errors: >> Generating INDEX-7 - please wait.. Done. >> make_index: hs-warp-0.3.2.3: no entry for /usr/ports >> make_index: hs-warp-0.3.2.3: no entry for /usr/ports Thanks for the report, I have just fixed it -- hopefully. Have a good time in Ottawa! :-) ___ 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: GHC Port on 9-CURRENT
Hi Eric, On 06/26/11 02:13, Eric McCorkle wrote: > The GHC (Glasgow Haskell Compiler) was marked broken by pointyhat > sometime back in May, following its update to GHC 7.0.3_1. I'm not > sure if anyone has looked at this, but it doesn't appear anyone has. Yes, you are right, sorry, I have not had time to take a closer look at this, but there is a log [1] for it on pointyhat (that I could not also reproduce on a -CURRENT system). > The GCC build succeeds Sounds great. > With Clang, an error occurs in one of the configure scripts, because > Clang warns about unused command-line arguments, and the configure > script assumes that to be a compiler error. You can deal with this by > adding -Qunused-parameter to CFLAGS. Thanks for investigating this. > However, the stage 1 compiler's parser appears to be broken, as it > reports erroneous parse errors on the GHC compiler's source code (and > probably for any haskell program, but it never gets a chance to). I'm > not sure why this happens, but I will investigate more closely once I > deal with some more important issues I'm investigating. I would be happy to see the logs. > In any case, the port builds fine with GCC. Perhaps it would be > prudent to set CC=gcc and CXX=g++ in the makefile for the time being > and mark the port as working again? Yeah, that might be a solution, I will try it. [1] http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/a.9.20110516102328/ghc-7.0.3.log ___ 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"
Heads Up: GHC 7.4.1 and Haskell Platform 2012.2.0.0
Hello there, For your information, there are new versions for the Haskell Platform [1] and the Glasgow Haskell Compiler [2] about to land in the next few days, and we have prepared the update in our GitHub repository for now. There you could take a look at them before they are scheduled for integration (some time after the official release, that is, around May 30, 2012): https://github.com/freebsd-haskell/freebsd-haskell/ In order to use the ports from this repository, you will have to install and configure portshaker(8). For further details, see the README file in the repository. After merging the ports trees, the Haskell Platform can be installed by the following command: # cd /usr/ports/devel/hs-haskell-platform/ && make install clean or updated in the conventional way, e.g. by portmaster(8) (together with other Haskell ports): # portmaster -r ghc Please let us (haskell@) know if you have any problems or concerns regarding the planned update. Thanks, Gabor [1] http://hackage.haskell.org/platform/ [2] http://www.haskell.org/ghc/ ___ 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: circular dependency issue
On Wed, Jan 9, 2013 at 2:06 PM, Joseph A. Nagy, Jr wrote: > I'm trying to install x11-wm/hs-xmonad but it keeps getting caught in a > circular dependency with print/hs-hscolour > > Is anyone else having issues with it? You get this if you have the option HSCOLOUR set. Disable this option for hs- ports (this is disable by default) or install/update print/hs-hscolour separately. The circular dependency is because HsColour cannot generate HsColourized documentation for itself -- so you will have to install it without HSCOLOUR first, then build it with HSCOLOUR, remove the old version and replace it with the new one. Or simply just omit the HsColourized documentation (or the documentation at all) for print/hs-hscolour. I am not sure that port update tools like portmaster, portupgrade and friends will support this so you will have to do it yourself manually. Hope that helps. ___ 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: Ocaml ports needs love
Hey there, On Wed, Feb 27, 2013 at 2:09 PM, b.f. wrote: > An ocaml alias and mailing list might help at least for the unmaintained > ports, and as a > place for discussions. Count me in! ___ 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] Glasgow Haskell Compiler 7.6.3, Haskell Platform 2013.2.0.0
Hi there,
Please note that the next version of the Haskell Platform is just
released [1], and we are also preparing a major update for the FreeBSD
Ports Collection as well. This also updates the Glasgow Haskell
Compiler to 7.6.3 [2] together with all the Haskell (hs-) ports to use
this.
The update is in our development repository [3]. We are planning to
commit this around beginning of next week if nothing critical shows up
during the testing.
You can test the upcoming changes easily as we are offering packages
in our custom pkg(8) repository:
http://haskell.inf.elte.hu/packages/
There you can find binary packages for FreeBSD 8.x (8.3 or later), 9.x
(9.1 or later), and 10.x (May 27, 2013 or later) for both i386 and
amd64 architectures. They can be used with pkg(8) in the following
way:
# env
PACKAGESITE=http://haskell.inf.elte.hu/packages/freebsd:$major:x86:$arch/latest/
pkg upgrade
where `major` is in {8,9,10} and `arch` is in {32,64}.
Note that some of the packages for 10.x is missing due to build
failures of some of the dependencies. If you want to experiment with
the ports themselves instead, you shall use portshaker(8) as described
at the GitHub page of our development repository [4].
Please send comments or submit bug reports directly to hask...@freebsd.org.
Thanks,
Gabor
[1] http://www.haskell.org/platform/
[2] http://www.haskell.org/ghc/
[3] https://github.com/freebsd-haskell/freebsd-haskell
[4] https://github.com/freebsd-haskell/freebsd-haskell/blob/master/README.md
___
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: Ocaml ports needs love
Hi Michael, On Tue, Jun 25, 2013 at 8:47 PM, Michael Grünewald wrote: > Besides maintaining individual ports, we also want to integrate GODI or > OASIS in ports, so it is probably a good idea to have a common place to > discuss these projects, to keep a list of open tasks and describe best > practices. I concur absolutely. Although my priority is rather to work with OPAM-based [1] packages. > A mailing list could be useful, as would a section on the wiki [1]. I can help with this. However, it basically requires a valid FreeBSD wiki registration (I am not sure if you have such account already). > I am pleased to announce that I improved my submission for OCaml-4.00 > [2] (there is still a minor issue) Great news! > and applied for a project ocaml-freebsd on OCamcore's forge. Let me know about the URL of the project once it is accepted and activated. [1] http://opam.ocamlpro.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"
Re: Ocaml ports needs love
On Sun, Jul 28, 2013 at 2:53 PM, John Marino wrote: > Is not opam already in ports? > http://www.freshports.org/devel/ocaml-opam/ Yeah, but OPAM 1.0.0 may not be the best choice for FreeBSD... Due to some trivial but annoying bugs OPAM will not work properly on FreeBSD. I am currently using the git version 83019d40090b7a44bd0e8a3b9ec4e55c4620df4d where those problems have been fixed. ___ 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: Ocaml ports needs love
On Tue, Jul 30, 2013 at 7:45 PM, Michael wrote: > Is it trivial to use the 1.0.0 port to build the version you are > referring to? OPAM does not need more just the vanilla OCaml compiler, for example 3.12.1 (that is, installing the current version from lang/ocaml) is okay. It can be then used to move to a different compiler version, using the following command: $ opam switch 4.00.1 It is because OPAM can also handle many different compiler toolchains. So, you can just do the following to install it for your user: $ git clone git://github.com/OCamlPro/opam $ cd opam $ ./configure --prefix=$HOME $ gmake $ gmake install > I would like to start using opam on FreeBSD to find out how it could be > incorporated to ports system. I guess once the OPAM 1.0.1 is out and the corresponding FreeBSD port is updated, it will be okay. ___ 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: Ocaml ports needs love
On Wed, Jul 31, 2013 at 6:38 PM, Michael wrote: > I am curious about how to > take advantage of OPAM for maintaining OCaml related ports. Actually, I have been also pondering this for a while already... :-) > The ideal > thing would be to have a `opam make-freebsd-port OPAMPACKAGE' subcommand > that would prepare a nice Makefile, pkg-descr, pkg-plist traid, ready to > plug in the ports hierarchy. OPAM looks quite independent and standalone to me: it maintains a separate directory (called ".opam") for its own files and does everything (stores tarballs, package database, repository indexes, state information, installed compilers, and such) there. I am not sure we could plug the FreeBSD Port Collection into this ecosystem, especially that OPAM can remove packages without much fuss (in contrast to Haskell Cabal, for example). > There is other language specific package managers—maybe Ruby GEMS and > Python EGGS, for instance—but I am not aware of how they interact with > the port system. Well, up to to my humble knowledge, only the Perl ports implement some way of integration with the Ports Collection, dubbed "BSDPAN" [1]. For the Haskell Cabal packages, ports are mostly geared towards providing proper removal, working around large build times, warranting that the given package builds fine on FreeBSD (especially with the components of the latest Haskell Platform), and pull in external dependencies when needed (for bindings, mostly). For what it is worth, an OPAM repository [2] is much like the ports tree but without Makefiles and with multiple versions of the same package and also stores compiler toolchains. The OPAM package description supports running on multiple platforms (i.e. can abstract away from differences like "make" versus "gmake") and allows to add patches to fix things in the source tarball. It can also get the sources directly from a git repository, and can manage overlapping multiple repositories, can stick packages to certain versions... In summary, I have a vague feeling that OPAM-managed packages can be maintained quite well without the help of the FreeBSD Ports Collection. We may want to offer pre-built FreeBSD binaries for some of the leaf ports (e.g. net/unison), though. [1] http://bit.ly/Jm8v20 [2] https://github.com/OCamlPro/opam-repository ___ 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: Ocaml ports needs love
On Thu, Aug 1, 2013 at 10:20 PM, Michael wrote:
> from the standpoint of a system administrator having two sets A and
> B of software packages managed by two different tools has a lot of
> drawbacks:
I am fully aware of all the issues you have summarized as I have been
maintaining the Haskell Cabal ports for the last 4-5 years, whose
number in the ports tree slowly exceeds 400 these days :-)
> I picture myself something like
> having an opam.bsd.mk makefile delegating all its work to opam, as in:
>
> do-build:
> ${CD} ${WRKSRC} opam build ${OPAMPACKAGENAME}
OPAM only has an "install" subcommand which is the build and the
install phase together. On the other hand, I do not think that OPAM
could work with standalone packages. It has to have a package index
where it stores all the metadata (i.e. the OPAM package and compiler
descriptions), but packages are still served via the regular OCaml
build solutions, such as OASIS.
As I wrote in my previous mail, OPAM is much like the reincarnation of
the ports tree itself in OCaml land.
> — OPAM manages its “own file hierarchy” and does not install binaries
> and so on at the regular places (I only glimpsed at this, tough).
It puts binaries under its own ".opam" state directory, depending on
which compiler is used. Note that because OPAM supports using
multiple different OCaml compilers (and switching between them),
personally I see it hard (if not impossible) to integrate with the
practices of the FreeBSD ports.
> A quick fix for this could be to have a dedicated installation, say
> something like “OPAMROOT=/usr/local/opam” and adding the relevant
> locations to the path (binaries and dll).
OPAM uses the "config env" subcommand to set all the relevant
environment variables for the currently used compiler toolchain, like
it sets the PATH each time, so the corresponding binaries are used to
build the packages. Bringing this to the level of the system (i.e.
prepend the OPAM directories to the system-level PATH value) might not
be the best solution.
Note that what FreeBSD ports would require is actually the build
"recipe", most of the other things can be then derived. So, we could
utilize the OPAM package descriptions to generate FreeBSD ports but
not OPAM itself.
> — OPAM does not distinguish between build and install while FreeBSD
> ports do.
Yes, it does not, see above.
> I think this is mostly a security issue: building does not require
> elevated privileges, only installing does. To support this separation,
> we would need to tweak OPAM for FreeBSD.
OPAM is indeed missing the separate "install" target in its package
description. I have not managed yet to learn why this design choice
was made...
> — We need to generate pkg-plist or extract an installation script or any
> similar information from an OPAM package.
>
> — We need to extract tarball location, dependancy information and
> descriptions from OPAM packages.
Been there, done that. For the Haskell Cabal ports, I have such a
tool, called hsporter [1] (which can also help with updating, by the
way).
> BTW I have a port for ocaml-4.00.1 (PR ports/173364) which still has a
> small issue — because other ports install docs in
> '/usr/local/share/doc/ocaml' , the directory will not be cleanly
> removed.
What ports? Other OCam ports (that depend on lang/ocaml)? Have you
tried @dirrmtry instead of @dirrm in the pkg-plist?
[1] https://github.com/freebsd-haskell/hsporter
___
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: State of the Porters' Handbook
On Mon, Oct 28, 2013 at 4:11 PM, Baptiste Daroussin wrote: > I do buy this argument :) and I'll see want I can do for that in the next > couple > of days. Please find a patch [1] (and see [2] for the HTML preview) for the porters-handbook document to address this problem. Note that some of the contents have been already updated by Eitan Adler, this is just a continuation of the work. [1] http://people.freebsd.org/~pgj/patches/2013/10/29/porters-handbook.staging.diff [2] http://people.freebsd.org/~pgj/patches/2013/10/29/porters-handbook-staging/ ___ 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: State of the Porters' Handbook
On Wed, Oct 30, 2013 at 3:32 PM, Eitan Adler wrote: > We generally don't refer to pkgng in the docs: please use "pkg". Well, I saw pkg written as "pkgng" in some other section (5.2.2.2. "PORTEPOCH") of the Porter's Handbook. Actually, I prefer to write it as pkg(8), but I am not sure if there has been a DocBook entity defined for it. > Further, I'd put the pkg cases first as the pkg_ tools are deprecated. I do not think that matters much. > + poudriere. These maintain > > Thanks for adding this. Note this is not complete. I believe poudriere would finally deserve an own section in the documentation, somewhere after Tinderbox. > + For ports that install kernel modules, the > > This should be in a different section specifically about kernel modules. This is related to staging, that is why it is there. I did not find any section on kernel modules, for what it is worth, the expression "kernel module" occurs only twice in the whole book -- hence I did not feel myself motivated to start a new section on kernel modules; at least, not for now. > + staging) but it is broken (Mailman up to 2.1.16, for instance). > > I would not mention specific ports here. Examples get old quick. I do not think this situation will change any time soon. > This looks good overall and thanks for working on it. Thanks for the feedback. ___ 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: Wacom driver
Dominic Fandrey wrote: > Gábor Kövesdán wrote: >> Dominic Fandrey escribió: >>> I have created a port of Bartosz Fabianowski's Wacom driver. >>> Since nobody has stepped forward to commit it, I thought I'd >>> inform this list, so that people can test it. >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=128547 >>> >> I suggest that you should consult with [EMAIL PROTECTED] He was going to >> port this >> driver himself but he hasn't got time so far. I've CC'd him because I >> don't think he is on the ports@ list because he is a doc committer. > > Well, I'm always willing to talk. However, I don't see much to be done > here. The port is done, I keep close contact to Bartosz and I'm > willing to maintain it. It's one of the few that actually installs a > module into /boot/modules, something that should be enforced more > thoroughly, in my opinion. > > Thanks to the ports Xorg magic I even don't have to take care of > dependencies. > Hello there, Thanks to Ping Cheng (maintainer of the original Linux driver), I already found and contacted Bartosz (at about middle of August), and I have tested some versions of his ported driver with my USB Wacom Bamboo. I asked him about an official FreeBSD port, but he replied he will do that himself (when it is time) :) I would be happy to see this driver in the Ports Collection, however I had serious problems with the latest version I tested (X crashed after a few minutes with Firefox and Gimp). It is a sorry, but I had to leave that configuration (6.3-STABLE on a desktop machine) behind (I had to move) and I switched to FreeBSD 7-PRERELEASE on a notebook meanwhile. I have not had time to test it again, though my Bamboo is next to my notebook :) (Therefore no physical limitations...) But if you need a committer for this port, I can offer you to look after your PRs, test and commit them (with some help from an experienced ports committer, of course). Cheers, :g ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OCAML version 3 (legacy)
Hi Euan, 2014-08-11 17:03 GMT+01:00 Euan Thoms : >However, I was suggesting we have a legacy port for OCAML 3.x, just >like we have for php and other important stuff that newer versions >breaks things. If you are really in need for the 3.x version of OCaml compiler, you may want to try OPAM [1]. That is the ocaml-opam package [2] in the FreeBSD repositories. Although OPAM is dubbed as a "package manager", it can actually manage different compiler versions, using its "switch" command [3]. Then you could install OCaml packages atop that compiler separately, isolated from other instances, giving the advantage of working with multiple OCaml versions at the same time. [1] https://opam.ocaml.org/ [2] http://www.freshports.org/devel/ocaml-opam [3] https://opam.ocaml.org/doc/Advanced_Usage.html ___ 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: OCAML version 3 (legacy)
2014-08-13 22:29 GMT+01:00 Euan Thoms : > How would dependency resolution be affected by your suggested method? OPAM manages the dependencies itself, without involving pkg(8). For what it is worth, you should be able to install unison via OPAM easily. Though, it will not put the unison binary to under /usr/local/bin but somewhere around ~/.opam/bin instead. > The context of my issue was that I needed a unison built with OCAML 3.x. Why? Will not the net/unison232 or the net/unison port simply work? They should be using the latest version of lang/ocaml already. ___ 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 Haskell mailing list
Hello there, For your information, the previously closed internal mail alias hask...@freebsd.org has become an open regular mailing list that you can subscribe to at lists.freebsd.org [1]. It is mainly for the ones who work on Haskell ports: compilers, third-party libraries, and frameworks, but it is open for people to stay informed on the progress, ask for help, and answer others about problems with the Haskell ports. Committers who want to touch Haskell ports are especially welcome here, but please coordinate on your efforts before making any major changes to them. Thanks, Gábor [1] https://lists.freebsd.org/mailman/listinfo/freebsd-haskell ___ 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"
Fwd: Call for FreeBSD 2014Q1 (January-March) Status Reports
Dear FreeBSD Community, Please note that the next submission date for the January to March Quarterly Status Reports is April 7th, 2014, about a month away. They do not have to be very long -- basically they may be about anything that lets people know what is going on around the FreeBSD Project. Submission of reports is not restricted to committers: Anyone who is doing anything interesting and FreeBSD-related can (and therefore encouraged to) write one! The preferred and easiest submission method is to use the XML generator [1] with the result emailed as an attachment to us, that is, mont...@freebsd.org [2]. There is also an XML template [3] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [4]. If you are still unsure what constitutes a good status report, check out the last issue [5]. To enable compilation and publication of the quarterly report as soon as possible for the April 7th deadline, please be prompt with any report submissions you may have. We are looking forward to all of your 2014Q1 reports! Thanks, Gabor [1] http://www.freebsd.org/cgi/monthly.cgi [2] mailto:mont...@freebsd.org [3] http://www.freebsd.org/news/status/report-sample.xml [4] http://www.freebsd.org/news/status/howto.html [5] http://www.freebsd.org/news/status/report-2013-10-2013-12.html ___ 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 FreeBSD 2014Q1 (January-March) Status Reports
Dear FreeBSD Community, Please note that the submission date for the January to March Quarterly Status Reports is, April 7th, 2014, about two weeks away. Please consult my previous message for the details: 2014-03-08 10:24 GMT+01:00 Gabor Pali : > They do not have to be very long -- basically they may be about > anything that lets people know what is going on around the FreeBSD > Project. Submission of reports is not restricted to committers: > Anyone who is doing anything interesting and FreeBSD-related can (and > therefore encouraged to) write one! > > The preferred and easiest submission method is to use the XML > generator [1] with the result emailed as an attachment to us, that is, > mont...@freebsd.org [2]. There is also an XML template [3] which can > be filled out manually and attached if preferred. For the expected > content and style, please study our guidelines on how to write good > status reports [4]. If you are still unsure what constitutes a good > status report, check out the last issue [5]. > > To enable compilation and publication of the quarterly report as soon > as possible for the April 7th deadline, please be prompt with any > report submissions you may have. > > We are looking forward to all of your 2014Q1 reports! > > Thanks, > Gabor > > > [1] http://www.freebsd.org/cgi/monthly.cgi > [2] mailto:mont...@freebsd.org > [3] http://www.freebsd.org/news/status/report-sample.xml > [4] http://www.freebsd.org/news/status/howto.html > [5] http://www.freebsd.org/news/status/report-2013-10-2013-12.html ___ 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 FreeBSD 2014Q1 (January-March) Status Reports
Dear FreeBSD Community, Please note that the submission date for the 2014Q1 aka. January to March 2014 Quarterly Status Reports is, April 7th, 2014, only 1 week away. Please consult my earlier message for the details: 2014-03-08 10:24 GMT+01:00 Gabor Pali : > They do not have to be very long -- basically they may be about > anything that lets people know what is going on around the FreeBSD > Project. Submission of reports is not restricted to committers: > Anyone who is doing anything interesting and FreeBSD-related can (and > therefore encouraged to) write one! > > The preferred and easiest submission method is to use the XML > generator [1] with the result emailed as an attachment to us, that is, > mont...@freebsd.org [2]. There is also an XML template [3] which can > be filled out manually and attached if preferred. For the expected > content and style, please study our guidelines on how to write a good > status report [4]. If you are still unsure what constitutes a good > status report, check out the last issue [5]. > > To enable compilation and publication of the quarterly report as soon > as possible for the April 7th deadline, please be prompt with any > report submissions you may have. > > We are looking forward to all of your 2014Q1 reports! > > Thanks, > Gabor > > > [1] http://www.freebsd.org/cgi/monthly.cgi > [2] mailto:mont...@freebsd.org > [3] http://www.freebsd.org/news/status/report-sample.xml > [4] http://www.freebsd.org/news/status/howto.html > [5] http://www.freebsd.org/news/status/report-2013-10-2013-12.html ___ 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 FreeBSD 2014Q1 (January-March) Status Reports
Dear FreeBSD Community, Please note that the submission date for the 2014Q1 aka. January to March 2014 Quarterly Status Reports is April 7th, 2014, that is today. Please consult my earlier message for the details: 2014-03-08 10:24 GMT+01:00 Gabor Pali : > They do not have to be very long -- basically they may be about > anything that lets people know what is going on around the FreeBSD > Project. Submission of reports is not restricted to committers: > Anyone who is doing anything interesting and FreeBSD-related can (and > therefore encouraged to) write one! > > The preferred and easiest submission method is to use the XML > generator [1] with the result emailed as an attachment to us, that is, > mont...@freebsd.org [2]. There is also an XML template [3] which can > be filled out manually and attached if preferred. For the expected > content and style, please study our guidelines on how to write a good > status report [4]. If you are still unsure what constitutes a good > status report, check out the last issue [5]. > > To enable compilation and publication of the quarterly report as soon > as possible for the April 7th deadline, please be prompt with any > report submissions you may have. > > We are looking forward to all of your 2014Q1 reports! > > Thanks, > Gabor > > > [1] http://www.freebsd.org/cgi/monthly.cgi > [2] mailto:mont...@freebsd.org > [3] http://www.freebsd.org/news/status/report-sample.xml > [4] http://www.freebsd.org/news/status/howto.html > [5] http://www.freebsd.org/news/status/report-2013-10-2013-12.html ___ 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: Frederic Culot takes over as portmgr-secretary@
Hey Thomas, 2014-05-16 18:27 GMT+02:00 FreeBSD Ports Management Team Secretary : > It is with great pleasure that the FreeBSD Ports Management Team announces > that Frederic (culot@) Culot will take over responsibilities of team > secretary effective immediately. I would like to thank you for all your contributions over the years as the secretary of the Port Management Team. I believe you did an great job and definitely set the bar high for Frederic. Anyhow, congratulations for Frederic at the same time, I think he is an excellent choice. ___ 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: Poudriere & Haskell ports "Options changed, deleting" every time
2014-05-21 17:24 GMT+02:00 J David : > Probably there is some > widget in the lang/ghc package that's needed to build the > documentation. Yes, there is. That is called Haddock, the documentation tool similar to Javadoc and Doxygen. Since it parses the same source code as the compiler itself, and the compiler tends to change quickly, they both come in the same package. Disabling the documentation disables the haddock tool, so the dependent Haskell Cabal packages cannot generate their documentation. ___ 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"
