Re: HandBrake port?

[Kurt Jaeger]

Hi!

> I'm attempting to install HandBrake on my FreeNAS version 9.3 in a jail.  I
> can not find a pkg for handbrake.  Can you provide me with the installation
> steps to install handbrake in a jail?  Or provide me with a link that shows
> how to install handbrake in a jail?

This should work:

cd /usr/ports/multimedia/handbrake
make install

but right now it seems to fail.

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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

[portscout]

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
+-+
dns/pear-Net_DNS2   | 1.4.0   | 1.4.1
+-+
math/plplot | 5.10.0  | 5.11.0
+-+


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

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: FreeBSD Port: Issue when ./configure is run

[Mathieu Arnold]

+--On 13 avril 2015 06:02:10 + Pracheth Javali 
wrote:
| I checked out the latest valgrind, but when I run ./configure, it throws
| me this:
| 
| checking for a supported OS... no (freebsd7.1)
| configure: error: Valgrind is operating system specific. Sorry.

This says you're running FreeBSD 7.1, which is not supported, you need to
be running 8.4, 9.3 or 10.1.

Regards,

-- 
Mathieu Arnold
___
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"

all those c++ ABI variations in ports

[Don Lewis]

A common problem lately has been triggered the conversion of
www/webkit-gtk* to USES=compiler:c++11-lib.  On FreeBSD 8 and 9, that
triggers the use of gcc 4.8 from ports and its bundled libstdc++.   A
lot of ports have also needed to also make this change even though they
don't use c++11.  Without this change, they fail build due to link
errors because they link in libstdc++ from base, which doesn't support
the new libstdc++ ABI that gcc48 expects.

I've been trying to get x11-fm/sushi to build and run on FreeBSD 8.4
(and also 9.3).  Since it links to webkit-gtk3, I tried changing to
USES=compiler:c++11-lib.  That didn't fix the problem and only changed
the error message.  I'm guessing the latter was do to using a newer
binutils from ports instead of the ancient one in base.  I was finally
able to make the build succeed by adding -lstdc++ to LDFLAGS.  This
turns out to be totally bogus since sushi appears to be totally written
in C and shouldn't need to link to libstdc++ at all.  It does link to a
number of C++ libraries, but presumably uses their C interfaces.  Some
of those libraries are built with gcc from base, which were linked to
the base libstdc++, and others were built with gcc 4.8 and linked to its
bundled libstdc++.  When sushi is linked, the version of libstdc++ that
gets linked into the application by rtld probably just depends on the
ordering of the libraries that request it.

Even after I got sushi to build, when I ran it, it seemed to go through
some initialization and then died with a SIGSEGV.  My suspicion was that
the cause was mixing c++ ABIs in one application.  I don't think that
gcc claims to support mixing gcc major versions within one C++
application because its C++ ABI has changed over time.  The libstdc++
library does using symbol versioning to try to be backwards compatible,
but what happens if the same object is manipulated by two different
versions of the ABI?

For more of the gory details: see


I found that there were three libraries used by sushi that were
expecting the base version of libstdc++: libgjs (lang/gjs), libmozjs
(lang/spidermonkey24), and libgraphite2.so (graphics/graphite2).  Since
the stack trace was deeply nested under a bunch of function calls in
libgjs and libmozjs, I changed those first. They were configured as
USES=compiler:c11, which seems pretty bogus since they are c++ libraries
and maybe c++0x would be more appropriate. Then I noticed that the logic
in Uses/compiler.mk was causing them to be built with with clang from
ports and linked to the base libstdc++.  I never even knew that was
possible!  But then, I see that's what the base version of clang in
FreeBSD 9.3 does.  After changing them to USES=compiler:c++11-lib to
force the using of gcc48 and its libstdc++, I was able to run sushi and
not experience any core dumps.  I am not able to verify that it actually
works correctly because gnome-shell is still broken, but it's looking
promising.

After changing graphics/graphite2 to USES=compiler:c++11-lib, I was able
to revert my changes to sushi and build it with base gcc once again
without any linker errors.

Unfortunately, this really seems to be a game of whack-a-mole, because
changing things to fix one port is likely to break others.  It also
seems to be wrong to start sprinkling USES=compiler:c++11-lib all over
the place.  Unfortunately that is currently the only way to force
linking to the newer version of libstdc++ to be compatible with other
C++11 ports.  Defaulting FAVORITE_COMPILER to gcc would help a lot,
especially on FreeBSD 8.  I think we have to bring in a compiler from
ports for pretty much any compiler:whatever, so bringing in gcc 48 and
getting the new libstdc++ would seem to be better than bringing in clang
and using the base libstdc++.   FreeBSD 9 is more problematical because
the base version of clang satisfies the requirements for most of the the
compiler settings, but unfortunately it uses the base libstdc++.
Defaulting FAVORITE_COMPILER to gcc would seem to be the best bet for 9.
Things look better for 10 and newer.  For the platforms with clang in
base, it can be used everywhere, and the only problem is likely to be
with C++ ports that USE_GCC=yes.  Platforms without clang are in the
same boat as FreeBSD 8.  This isn't painless by any means.  Some of the
ports that switch from building with clang to gcc will probably be found
to ignore LDFLAGS, which is needed to specify the rpath for the ports
gcc libstdc++.  Also some ports will probably need USES=compiler
additions.

I still don't have an answer as to why building lang/gjs and
lang/spidermonkey24 with clang causes sushi to core dump, but debugging
that is very low on my priority list.

___
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: MooseFS Ports for versions 2.0 and 3.0

[Piotr Robert Konopelko]

Thank you very much for this information.

I posted requests to the FreeBSD bugzilla:

https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs&list_id=56910[1]
 


-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer* | moosefs.com[2]


Those ports currently have their maintainer fields set to 
"po...@freebsd.org[3]", meaning 
there is no maintainer.

When you submit the bug report and attach your patch to update the port, simply 
ensure 
the maintainer email address is updated to your own. You will then be 
volunteering as 
the maintainer for those ports.

Regards,Ben


On Thu, 9 Apr 2015 at 9:12 pm Fernando Apesteguía 
 wrote:


El 09/04/2015 15:00, "Piotr Robert Konopelko" 
escribió:>> Dear FreeBSD Ports team,>> On 
FreeBSD 
Ports site only ports for MooseFS 1.6.27-5 are available:> 
https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[1][6]
https://bugs.freebsd.org/bugzilla/[7]
moosefs.com[2][2]>>> > [1] 
https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[8]
http://moosefs.com[2]
freebsd-ports@freebsd.org[9] mailing list> 
http://lists.freebsd.org/mailman/listinfo/freebsd-ports[10]
freebsd-ports-
unsubscr...@freebsd.org[11]"___

freebsd-ports@freebsd.org[9] mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-ports[10]
freebsd-ports-unsubscr...@freebsd.org[11]"




[1] 
https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs&list_id=56910
[2] http://moosefs.com
[3] mailto:po...@freebsd.org
[4] mailto:fernando.apesteg...@gmail.com
[5] mailto:piotr.konope...@moosefs.com
[6] https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[1]
[7] https://bugs.freebsd.org/bugzilla/
[8] https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all
[9] mailto:freebsd-ports@freebsd.org
[10] http://lists.freebsd.org/mailman/listinfo/freebsd-ports
[11] mailto:freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HandBrake port?

[Ben Woods]

It looks like a few volunteers have been putting in some good effort to get
this port working (thanks to Walter Schwarzenfeld and kwhite). The patch
which is needed to make this work is not committed yet, but is attached to
PR199126 here and awaiting a committer:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126

To build this port with this patch:
$ cd ~
$ fetch -o handbrake.patch "
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155525";
$ cd /usr/ports
$ sudo patch -p0 < ~/handbrake.patch

Then build and install the port as per normal.

Regards,
Ben

On Mon, Apr 13, 2015 at 3:16 PM Kurt Jaeger  wrote:

> Hi!
>
> > I'm attempting to install HandBrake on my FreeNAS version 9.3 in a
> jail.  I
> > can not find a pkg for handbrake.  Can you provide me with the
> installation
> > steps to install handbrake in a jail?  Or provide me with a link that
> shows
> > how to install handbrake in a jail?
>
> This should work:
>
> cd /usr/ports/multimedia/handbrake
> make install
>
> but right now it seems to fail.
>
> --
> p...@opsec.eu+49 171 3101372 5 years to
> go !
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: MooseFS Ports for versions 2.0 and 3.0

[Ben Woods]

Nice work putting the ports together - its a good first effort! I have a
few comments about the format of the ports and bug reports - sorry there
are quite a few. I don't mean to be picky, but I wanted to minimise the
back-and-forth for you to get these committed.

1. Updates to existing ports should be attached as patches to the current
ports tree. The easiest way to do this if you got the ports tree from
subversion (not portsnap) is using the svn diff command. Tick the "patch"
option when attaching so we can see a nice pretty diff from within bugzilla.

2. New ports should be attached as a shar(1) file. Assuming the port is
called oneko, cd to the directory above where the oneko directory is
located, and then type: shar `find oneko` > oneko.shar

3. It's nice for ports for share parts of their configuration, but I don't
think it should be called "bsd.port.moosefs.mk" (this implies it is part of
the port build scripts). A good example of what you could do
is devel/libtool. It has a Makefile which includes Makefile.common. The
devel/libltdl port also includes "${.CURDIR}/../libtool/Makefile.common".

4. @dirrm is now deprecated in pkg-plist. Suggest it is probably easier to
build this with "make install && make makeplist > pkg-plist". Note that you
should check the plist looks correct, and also delete the top warning line
from the generated file.

5. The pkg-descr file should be updated to include a better description of
the package, and link to the website.

6. Before submitting a port, check that it passes the normal checks by
installing the ports-mgmt/portlint program, and running "portlint -AC" in
the port directory.

7. If you have access to a poudriere installation, you should submit the
"poudriere testport" logs showing that this port will build successfully.
Myself or other ports contributors/committers can help with this if you do
not have access to a poudriere installation, but please make sure you have
at least tested the build on FreeBSD with a "make install".

Much of this is covered in the porter's handbook. It's a good read if you
haven't already seen it. You can find it here:
https://www.freebsd.org/doc/en/books/porters-handbook/book.html

Note that if you re-submit patches to each bug report, be sure to tick the
option that it obsolete's the previous patch.

Good luck! :)

Regards,
Ben

On Mon, Apr 13, 2015 at 7:05 PM Piotr Robert Konopelko <
piotr.konope...@moosefs.com> wrote:

>  Thank you very much for this information.
>
>
>
> I posted requests to the FreeBSD bugzilla:
>
>
>
>
> https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs&list_id=56910
>
>
>
>
>
> --
>
> Best regards,
>
> Piotr Robert Konopelko
>
> MooseFS Technical Support Engineer | moosefs.com
>
>
>
>
> On Thursday 09 of April 2015 2:52:32 PM Ben Woods wrote:
>
> Those ports currently have their maintainer fields set to "
> po...@freebsd.org", meaning there is no maintainer.
>
> When you submit the bug report and attach your patch to update the port,
> simply ensure the maintainer email address is updated to your own. You will
> then be volunteering as the maintainer for those ports.
>
> Regards,
> Ben
>
> On Thu, 9 Apr 2015 at 9:12 pm Fernando Apesteguía <
> fernando.apesteg...@gmail.com> wrote:
>
> El 09/04/2015 15:00, "Piotr Robert Konopelko"  >
> escribió:
> >
> > Dear FreeBSD Ports team,
> >
> > On FreeBSD Ports site only ports for MooseFS 1.6.27-5 are available:
> > https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[1]
> >
> > Longer than a half year ago MooseFS 2.0 has been released and few days
> ago - MooseFS
> > 3.0.
> >
> > We would like to inform, that we have prepared ports for MooseFS versions
> 2.0 and 3.0.
> >
> > How is the way to upgrade them in FreeBSD ports tree?
>
> You can start here:
>
> https://bugs.freebsd.org/bugzilla/
>
> And file a request
>
> > Is there a possibility to make our team the maintainer of the MooseFS
> FreeBSD Ports?
>
> Since ports@ is the current maintainer, you could file another request and
> see if they are willing to drop mantainership in your favor or ask here :)
>
> >
> >
> > --
> > Best regards,
> > Piotr Robert Konopelko
> > *MooseFS Technical Support Engineer* | moosefs.com[2]
> >
> >
> > 
> > [1] https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all
> > [2] http://moosefs.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"
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
>
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@f

Re: HandBrake port?

[Kurt Jaeger]

Hi!

> It looks like a few volunteers have been putting in some good effort to get
> this port working (thanks to Walter Schwarzenfeld and kwhite).
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126

Is this also tested on 9.3-amd64 ?

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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"

(GSoC 2015) Parallel ports build and installation => paraports

[rank1seeker]

Hello,

I've posted this last week @hackers and was advised to repost on this
list.

So, ...
It is application for configuring, fetching, building and installing software 
(ports) on FreeBSD
It provides a safe way for building AND installation of several ports 
simultaneously by taking care of order of dependencies.
Each build process is independent of others with it's own dir where output 
(separated in 2 files, one for STDOUT and second for STDERR) is stored in case 
if build error occurs.

Number of simultaneous builds depends on chosen amount of jobs, which defaults 
to 2 jobs per core.
1 core CPU performed fastest with 2 jobs = 2 simultaneous builds
Allows multicore machines to use all its potential

It also supports building AND installation in DESTDIR, which is demonstrated in 
video below.
With -e flag enables all '-o' installed origins in rc.conf

Best part => whole implementation is solely based on FreeBSD's base userland 
tools
/bin/sh (+awk/sed/etc ...)


To cut it short, here is unfinished working code: (because I could type and 
type lengthy description and am short on time)
http://www.starforce.biz/paraports.mp4

I'll respond to questions (I bet it'll start with "why so much in configs").
;)


Mentor:
---
I would prefer to get mentor during this week.
I understand theirs time is tight for mentorship, so it is a plus that I 
already have a working code demonstrated above and also understand whole 
process, so mentor's time consumption will be minimal.

Thanks in advance.

PS: I'm not subscribed to port's list, only @hackers, so keep me in To:, Cc:, 
...


Domagoj Smolčić
___
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: HandBrake port?

[Mathieu Arnold]

+--On 13 avril 2015 16:37:03 +0200 Kurt Jaeger  wrote:
| Hi!
| 
|> It looks like a few volunteers have been putting in some good effort to
|> get this port working (thanks to Walter Schwarzenfeld and kwhite).
|> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126
| 
| Is this also tested on 9.3-amd64 ?

And 8.4 ?

-- 
Mathieu Arnold
___
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: HandBrake port?

[Kurt Jaeger]

Hi!

> |> It looks like a few volunteers have been putting in some good effort to
> |> get this port working (thanks to Walter Schwarzenfeld and kwhite).
> |> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126

> | Is this also tested on 9.3-amd64 ?

> And 8.4 ?

It builds on 10.1a, 9.3a and 8.4i, so I'll commit the patch.

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: HandBrake port?

[Dave]

On Monday 13 April 2015 17:51:39 Kurt Jaeger wrote:
> Hi!
> 
> > |> It looks like a few volunteers have been putting in some good effort to
> > |> get this port working (thanks to Walter Schwarzenfeld and kwhite).
> > |> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126
> 
> > | Is this also tested on 9.3-amd64 ?
> 
> > And 8.4 ?
> 
> It builds on 10.1a, 9.3a and 8.4i, so I'll commit the patch.
> 
> 
Thank you.

I just did a portsnap/portupgrade and confirm that it compiles and runs on 9.3.
___
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: Initial squid 3.5 port

[Kurt Jaeger]

Hi!

> The squid35 port has been updated to lastest 3.5.3 release.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
> This time it's a patch for the existing www/squid.
> Please, test it and write a feed back!
> 
> IMO it's ready to import.

I build-tested it and it looks fine. There is still the
issue with building it with the base kerberos on a host where
one of the kerberos ports is installed. For those cases, use
poudriere.

I will update the port in approx. 24 hours if there are no reports
of things breaking. So please test it 8-}

Thanks to Pavel for his hard work and persistence!

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: Initial squid 3.5 port

[John Marshall]

On Mon, 13 Apr 2015, 20:28 +0200, Kurt Jaeger wrote:
> > The squid35 port has been updated to lastest 3.5.3 release.
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
> > This time it's a patch for the existing www/squid.
> > Please, test it and write a feed back!

> I will update the port in approx. 24 hours if there are no reports
> of things breaking. So please test it 8-}

I have just tested on the following platforms with good results.  I use
Kerberos (base system) for client GSSAPI authentication and LDAP groups
to control access to destinations for those clients: they were the bits
I was nervous about but all is good!

 r281234 10.1-RELEASE-p9 amd64
 r281234 10.1-STABLE i386

Thank you for working on this!

-- 
John Marshall


pgpzA70tD9rGL.pgp
Description: PGP signature

Poudriere build fails on several ports with leftovers message for info/dir

[Yuri]

This seems to be the serial error related to turned off docs.

/etc/make.conf has these unsets:
OPTIONS_UNSET=DOCS HTMLDOCS HELP PORTDOCS APIDOCS RDOC MANPAGES EXAMPLES 
PORTEXAMPLES


Here is the message:
>> Error: Files or directories left over:
info/dir

Example ports:
security/libassuan
security/libgcrypt
security/libksba

poudriere is run with -t of course

Yuri
___
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: MooseFS Ports for versions 2.0 and 3.0

[Piotr Robert Konopelko]

Hello Ben,

Thank you very much for your reply and your time!

We'll implement your notes into our ports :)

-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer* | moosefs.com[1]


Nice work putting the ports together - its a good first effort! I have a few 
comments 
about the format of the ports and bug reports - sorry there are quite a few. I 
don't mean 
to be picky, but I wanted to minimise the back-and-forth for you to get these 
committed.



1. Updates to existing ports should be attached as patches to the current ports 
tree. The 
easiest way to do this if you got the ports tree from subversion (not portsnap) 
is using the 
svn diff command. Tick the "patch" option when attaching so we can see a nice 
pretty diff 
from within bugzilla.


2. New ports should be attached as a shar(1) file. Assuming the port is called 
oneko, cd to 
the directory above where the oneko directory is located, and then type: shar 
`find oneko` 
> oneko.shar


3. It's nice for ports for share parts of their configuration, but I don't 
think it should be 
called "bsd.port.moosefs.mk[2]" (this implies it is part of the port build 
scripts). A good 
example of what you could do is devel/libtool. It has a Makefile which includes 
Makefile.common. The devel/libltdl port also 
includes "${.CURDIR}/../libtool/Makefile.common".


4. @dirrm is now deprecated in pkg-plist. Suggest it is probably easier to 
build this with 
"make install && make makeplist > pkg-plist". Note that you should check the 
plist looks 
correct, and also delete the top warning line from the generated file.


5. The pkg-descr file should be updated to include a better description of the 
package, 
and link to the website.


6. Before submitting a port, check that it passes the normal checks by 
installing the ports-
mgmt/portlint program, and running "portlint -AC" in the port directory.


7. If you have access to a poudriere installation, you should submit the 
"poudriere 
testport" logs showing that this port will build successfully. Myself or other 
ports 
contributors/committers can help with this if you do not have access to a 
poudriere 
installation, but please make sure you have at least tested the build on 
FreeBSD with a 
"make install".




Much of this is covered in the porter's handbook. It's a good read if you 
haven't already 
seen it. You can find it here:
https://www.freebsd.org/doc/en/books/porters-handbook/book.html[3]



Note that if you re-submit patches to each bug report, be sure to tick the 
option that it 
obsolete's the previous patch.


Good luck! :)


Regards,
Ben


On Mon, Apr 13, 2015 at 7:05 PM Piotr Robert Konopelko 
 wrote:


Thank you very much for this information.
 
I posted requests to the FreeBSD bugzilla:
 
https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs&list_id=56910[5]
 
 
 
-- 
Best regards,
Piotr Robert Konopelko
*MooseFS Technical Support Engineer* | moosefs.com[1]


Those ports currently have their maintainer fields set to 
"po...@freebsd.org[6]", meaning 
there is no maintainer.

When you submit the bug report and attach your patch to update the port, simply 
ensure 
the maintainer email address is updated to your own. You will then be 
volunteering as 
the maintainer for those ports.

Regards,Ben


On Thu, 9 Apr 2015 at 9:12 pm Fernando Apesteguía 
 wrote:


El 09/04/2015 15:00, "Piotr Robert Konopelko" 
escribió:>> Dear FreeBSD Ports team,>> On 
FreeBSD 
Ports site only ports for MooseFS 1.6.27-5 are available:> 
https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[1][8]
https://bugs.freebsd.org/bugzilla/[9]
moosefs.com[1][2]>>> > [1] 
https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[10]
http://moosefs.com[1]
freebsd-ports@freebsd.org[11] mailing list> 
http://lists.freebsd.org/mailman/listinfo/freebsd-ports[12]
freebsd-ports-
unsubscr...@freebsd.org[13]"___

freebsd-ports@freebsd.org[11] mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-ports[12]
freebsd-ports-unsubscr...@freebsd.org[13]"


___
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"