Re: The ports@ list is now subscriber-post only

[Tilman Keskinöz]

On 12/09/2017 17:27, Adam Weinberger wrote:
> The po...@freebsd.org (aka freebsd-ports@) mailing list now requires you
> to subscribe to the list before posting. This brings us two important
> benefits:
> 
> * This should cut back tremendously on spam coming through the list.

I must be living in a parallel universe, checking
https://lists.freebsd.org/pipermail/freebsd-ports/2017-December/thread.html
there has been one (1) spam message getting through so far this month.
That's a really tremendous amount of spam.

> * Users are more likely to find better answers to their questions: The
> first three times a question is asked, it gets detailed replies. The
> fourth through nth times usually get a one sentence reply.

Is a moderator ensuring that messages from unsubscribed users, who just
sent a mail to the maintainer of an unmaintained port get through?

Otherwise we will probably miss a lot of bug reports from Users who
don't bother to subscribe.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADUP] FLAVORS landing.

[Tilman Keskinöz]

On 2017-09-27 08:29, Matthew Seaman wrote:
> On 27/09/2017 07:11, Julian Elischer wrote:
>> Is there a document/paper on what this is and what it's limits are etc?
> 
> https://wiki.freebsd.org/Ports/FlavorsAndSubPackages
> https://wiki.freebsd.org/Ports/FlavorsMigration
> 

These pages don't contain any information what this is, how it differs
from/interacts with the OPTIONS framework and why I would want to
convert a port to FLAVORS.






signature.asc
Description: OpenPGP digital signature

Re: devel/aws-sdk-cpp

[Tilman Keskinöz]

Hi,

According to pkg-plist the header file should be installed. Did you
install from ports or binary packages?

Try to reinstall it.


On 2017-08-09 20:30, Wayne Marsh wrote:
> Hey all, I installed the aws-sdk-cpp port, and I'm trying to use the EC2
> API.  But I get a legit error that
> /usr/local/include/aws/ec2/model/InstanceHealthStatus.h doesn't exist.  Any
> idea why only a partial SDK was installed and what I might do to correct
> the issue?  I'm running FreeBSD 11.0 RELEASE.
> 
> I have successfully used the CloudWatchLogs client, and I'm actually
> extending that code.  I'm a little baffled by the missing include file
> which is depended on by another present include file.  I have no idea where
> to start looking as Google raises no hints while searching for an answer.



signature.asc
Description: OpenPGP digital signature

Re: How to create a port with uncompressed distfile?

[Tilman Keskinöz]

* Darren Pilgrim [Thu, 27 Nov 2014 10:37:19 -0800]:
>> The last one i did not get right. I believe i have to use
>> ${INSTALL_PROGRAM} but i make something wrong. Can somebody help?
> 
> Add "STRIP=" as a line after the NO_BUILD line, then in the do-install
> target:
> 
> ${INSTALL_PROGRAM} ${WRKSRC}/${DISTNAME}${EXTRACT_SUFX} \
> ${STAGEDIR}${PREFIX}/bin/phpunit
> 

Better use INSTALL_SCRIPT



signature.asc
Description: OpenPGP digital signature

Re: iconv in base breaks multiple ports

[Tilman Keskinöz]

hi Ulrich,

* Ulrich Spörlein [Sun, 20 Oct 2013 20:27:23 +0200]:
> ever since that iconv thing replaced the ports version, I run into
> trouble with several ports that I have installed on a -CURRENT (now
> stable/10 system).
> 
> These are not compile-time errors, but crashes or limited functionality
> where I blame iconv :)
> 
> 
> 1. www/newsbeuter crashes during startup, somewhere in the stfl code
> that deals with wide char functions.
> 

> Is my system hexed? I've rebuilt the ports/packages a dozen times now.
> Am I seeing ghosts?


I don't run Current, but according to the pkg-fallout mails i am
receiving, newsbeuter shouldn't even compile on CURRENT. Maybe there are
some stale files on your system?

There is also an update in the PR system, you might want to try,
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182896






___
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: last.fm

[Tilman Keskinöz]

* ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]:

> I got an email about last fm and a new version:
> 
> "We're writing you to let you know that there will soon be a change to 
> Last.fm 
> radio that may affect you. Our stats show that you've listened to radio 
> through 
> an application that uses our old streaming protocol. On 1 December we will 
> deprecate this old protocol, so in some applications radio will no longer 
> work.
> 
>  If you would like to continue enjoying Last.fm Radio, consider upgrading to 
> a 
> new application or using http://www.last.fm/listen

I have prepared a patch to update the port.

Unfortunately i have not been able to test it yet.

http://people.freebsd.org/~arved/stuff/patch.last.fm

Please report back, if it works
arved



___
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: Jenkins+FreeBSD handbooks

[Tilman Keskinöz]

* Marin Atanasov Nikolov [Mon, 6 Aug 2012 13:40:52 +0300]:
>> Redports is a public compile testing environment for FreeBSD ports. So like
>> Ports Tinderbox but with a nice multiuser GUI, cluster functionality for
>> scaling and an own Subversion tree for the users to commit their ports to.
>>
>> Before I decided to write the code myself I had a closer look at Bitten and
>> Jenkins. Both could be made into what redports is now but they all have
>> their weak spots. Jenkins GUI looks very cluttered and is quite hard to
>> understand if you just want to manually schedule a few new jobs for your
>> ports as Joe Average. It's also quite hard to understand and complex as a
>> developer and administrator so I was concerned that fixing it if it breaks is
>> non trivial. Not to talk about all the special customizations that we need
>> which would require me to write extensions in Java and understand how
>> all that jenkins internals work.
>>
> 
> Like any other system Jenkins has it's own learning curve as well, but
> once you get to know it,
> you see how intuitive it is to use the system.
> 
> I agree with you on the Java stuff. That's the one thing I don't like
> about Jenkins being Java..
> 
> But I can tell from my experience with it so far, that I haven't had
> any issues with it, e.g. breaking and spending lots of time figuring
> out how to fix it. Maybe one day I will, but so far I'm quite happy
> with it :)


>>> Jenkins comes with lots of ready-to-use plugins as well, which makes
>>> it easier to integrate a particular thing easier as well and not
>>> re-invent the wheel.

I am surprised you haven't run into any plugin incompatibilities.

We use Jenkins at work and have frequently hard to debug issues with
plugins being incompatible with certain jenkins versions or with other
plugins.
Sometimes a broken plugin manages to take down the whole Jenkins,
sometimes there are just random Java backtraces causing build failures
in projects.

IMHO the whole Jenkins architecture is way too fragile to be used for
large projects like FreeBSD.


___
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: no MAINTAINER for postgresql90-client

[Tilman Keskinöz]

* Robert Huff [Tue, 5 Jun 2012 09:53:37 -0400]:

> 
>   The Makefile has no MAINTAINER line.
>   Is this deliberate?  If so, why?
>   And who do I contact about a problem building this port?
> (Tarball doesn't fetch.)
> 

In the ports directory type

make maintainer
___
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] cvs commit: ports/devel/rubygem-daemons Makefile distinfo

[Tilman Keskinöz]

On Jan 28, 2012, at 20:22 , Philip M. Gollucci wrote:

> On 1/28/12 1:52 AM, Tilman Keskinöz wrote:
>> If there is no reason, the port should be either fixed, or the commit backed 
>> out!
> This is not a unique problem among gems.  Lots of them screw up umasks on 
> install.  Some too restrictive, some overly lax.

The committer committing the patch is responsible for testing the port for 
screw ups.

No port should install world-writable scripts or executables. This is a 
security issue. Again i ask you to fix the port or backout your commit.

In the old days, Kris processed the pointyhat logs for these issues[1]. Maybe 
someone with access to the pointyhat logs can do this again?

Also how about introducing a Makefile variable "WORLDWRITABLE_FILES" for the 
highscore files and aborting the install if a file is not mentioned in this 
variable.

[1] e.g. 
http://lists.freebsd.org/pipermail/freebsd-ports/2006-September/035115.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: Can't compile kde4 and kdelibs4 with an uptodate amd64 Releng machine. (

[Tilman Keskinöz]

There has been a thread on the cvs-ports Mailinglist about this with the
subject "cvs commit: ports/Mk bsd.cmake.mk"

and there is a bugreport
https://bugs.kde.org/show_bug.cgi?id=276461



* Conrad J. Sabatier [2011-16-21 23:16]:
> On Mon, 21 Nov 2011 17:27:42 +0100
> Olivier Smedts  wrote:
> 
>> 2011/11/21 Conrad J. Sabatier :
>>> On Mon, 21 Nov 2011 07:42:43 -0600
>>> eculp  wrote:

 I have tried building both from the different ports and even more
 using portmaster and all stop ate similar locations in kdelabs4.
 Maybe there is something that I should or could build first.

 errors follow:

 kdelibs stops here:


 [  1%] Built target krosscore_automoc
>>>
>>> So where are the errors?  There are none in the output you posted.
>>
>> I think there's no error (if it's the same problem as mine).
>>
>> For me, the build process seems to stop/freeze randomly, most often
>> after "Built target XXX". It affects only KDE ports, no other
>> qt4-qmake or cmake consumer. No CPU usage. No disk usage. No excessive
>> or changing memory usage... I didn't report it earlier because I don't
>> know how to debug this, and it did not seem to affect other users
>> (until now).
> 
> OK, I didn't get that point from the original poster.  I was looking to
> see some actual error output.
> 
>> Here is the "workaround" I painfully used on my 2 desktop machines :
>>
>> # cd /usr/ports/x11/kde4
>> # make
>> wait for a freeze...
>> ^C
>> # make
>> wait for a freeze...
>> ^C
>> # make
>> ...
>> I maybe had to restart the build one or two hundred times to have a
>> fully installed KDE4.
> 
> Wow, "painful" is an understatement here, to say the least.  :-)
> 
> Have you tried using truss or ktrace to see what's going on when these
> "freezes" occur?
> 
> You'll want to be sure to enable tracing descendents of the original
> make process as well.  Ports makes, as you no doubt are aware, spawn
> numerous processes along the way.
> 
> truss -f make
> (or)
> ktrace -i make
> 
> See the man pages for other options you may want to use as well.
> 
> ktrace, in particular, will produce *copious* output.  You'll probably
> want to just do a "tail" on the generated ktrace.out file:
> 
> kdump | tail - | more
> 
>> I've got this behavior since KDE 4.7.X (4.7.2 and 4.7.3), I had no
>> problems building KDE 4.6.X.
>>
>> I even tried deleting all ports, cleaning /usr/local, tried again. No
>> change. Tried compiling all ports with gcc instead of clang, no
>> change. Forced make jobs UNSAFE, no change.
>>
>> I use FreeBSD 9.0 amd64, system built with clang (are you ?).
> 
> No, I only use the default system gcc:
> 
> # gcc -v
> Using built-in specs.
> Target: amd64-undermydesk-freebsd
> Configured with: FreeBSD/amd64 system compiler
> Thread model: posix
> gcc version 4.2.1 20070831 patched [FreeBSD]
> 
>> %cat /etc/make.conf
>> SVN_UPDATE=yes
>> SVN=/usr/local/bin/svn
>> CPUTYPE?=core2
> 
> I've been using the (undocumented, at least in /etc/make.conf)
> CPUTYPE?=native with no problems for quite some time now.  Let gcc
> detect the processor type and generate the appropriate code.
> Eliminates any guesswork in trying to select the correct setting for
> CPUTYPE.
> 
>> KERNCONF=CORE
>> CFLAGS=-O2 -pipe -march=core2 -fomit-frame-pointer
> 
> There's no need to add -march= to CFLAGS, if you're setting CPUTYPE
> (that's what CPUTYPE is for).
> 
>> NO_CPU_CFLAGS=yes
> 
> Why are you setting CPUTYPE, and then telling make not to use it?  And
> then, setting the CPU type anyway in your CFLAGS?  :-)
> 
>> COPTFLAGS=-O2 -pipe -march=corei7 -fomit-frame-pointer
>> NO_CPU_COPTFLAGS=yes
> 
> Again, same question as above.
> 
> Even more pointedly, why core2 in CFLAGS and corei7 (what is that?) in
> COPTFLAGS?
> 
>> BOOTWAIT=0
>> WITHOUT_PROFILE=yes
> 
> Yes, WITHOUT_PROFILE=yes is the most sensible choice for most users.
> Should be enabled by default, IMHO.
> 
>> .if !${.CURDIR:M/usr/ports/deskutils/kdepimlibs4*} &&
>> !${.CURDIR:M/usr/ports/devel/icu*} &&
>> !${.CURDIR:M/usr/ports/editors/kate*} &&
>> !${.CURDIR:M/usr/ports/games/kdegames4*} &&
>> !${.CURDIR:M/usr/ports/graphics/libwpg*} &&
>> !${.CURDIR:M/usr/ports/graphics/netpbm*} &&
>> !${.CURDIR:M/usr/ports/graphics/vigra*} &&
>> !${.CURDIR:M/usr/ports/multimedia/kdemultimedia4*} &&
>> !${.CURDIR:M/usr/ports/net/hupnp*} &&
>> !${.CURDIR:M/usr/ports/net/kdenetwork4*} &&
>> !${.CURDIR:M/usr/ports/textproc/libwpd*} &&
>> !${.CURDIR:M/usr/ports/textproc/libwps*} &&
>> !${.CURDIR:M/usr/ports/www/firefox*} &&
>> !${.CURDIR:M/usr/ports/www/libxul*} &&
>> !${.CURDIR:M/usr/ports/www/qt4-webkit*} &&
>> !${.CURDIR:M/usr/ports/x11/kde4-baseapps*} &&
>> !${.CURDIR:M/usr/ports/x11/kde4-runtime*} &&
>> !${.CURDIR:M/usr/ports/x11/kde4-workspace*} &&
>> !${.CURDIR:M/usr/ports/x11/kdelibs4*}
>> .if !defined(CC) || ${CC} == "cc"
>> CC=clang
>> .endif
>> .if !defined(CXX) || ${CXX} == "c++"
>> CXX=clang++
>> .endif
>> .if !defined(CPP) || ${CPP} == "cpp"
>> CPP=clang -E
>> .endif
> 

Re: Time to mark portupgrade deprecated?

[Tilman Keskinöz]

On 07/25/2011 04:20 AM, Eitan Adler wrote:
> At this point noone is maintaining portupgrade any more and a large
> number of PRs have been filed against it (see
> http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No
> one has stepped up to do the work to fix these bugs so it is time to
> officially drop it.
> 
> 

I shortly went through the list.

There are currently 22 PRs filed against portupgrade

Of these:

4   are general problems of the ports collection/pkg_tools.
(architecture-specific INDEX, Detecting of OPTIONs set,
Overriding/removing files changed by the user etc.)

2   are documentation bugs

1   wishlist item

4   contain patches

1   i believed is already fixed, i set to feedback.

So this leaves the following, which need someone (a maintainer?) to
investigate/write a patch:

  112818 ruby portsopen  non-criti medium   current-us
ports-mgmt/portupgrade -a fails with database error
  127019 ruby portsopen  serious   medium   current-us
ports-mgmt/portupgrade does not recognize fail conditions
  127889 ruby portsopen  non-criti low  current-us
ports-mgmt/portupgrade detects spurious failures and skips ports
unnecessarily
  129930 ruby portsopen  serious   high current-us
ports-mgmt/portupgrade - portinstall tries to install dependencies twice
  13 ruby portsopen  serious   medium   current-us
ports-mgmt/portupgrade-devel: completely removes package on installation
error
  140008 ruby portsopen  non-criti medium   current-us
ports-mgmt/portupgrade-devel chokes on bsdpan pkgs
  147242 ruby portsopen  critical  medium   current-us
ports-mgmt/portupgrade incorrectly remove old port when new one fails to
compile
  151662 ruby portsopen  non-criti low  current-us
ports-mgmt/portupgrade: upgrade of autoconf leaves old version
  154210 ruby portsopen  serious   medium   current-us
ports-mgmt/portupgrade 2.4.8_1,2: cross-thread violation on rb_gc()

IMHO the situation is not that bad, that we need to DEPRECATE 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: Time to mark portupgrade deprecated?

[Tilman Keskinöz]

On 07/25/2011 04:20 AM, Eitan Adler wrote:
> At this point noone is maintaining portupgrade any more and a large
> number of PRs have been filed against it (see
> http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No
> one has stepped up to do the work to fix these bugs so it is time to
> officially drop it.

Despite the fact that there are many PRs about it, it still works for
most users i guess.

I am ok with switching the documentation to portmaster, but i am against
marking it DEPRECATED. I have been using portupdate for 10 years and it
works for all my usecases.

Switching to portmaster means i have to learn new -options and new error
messages. Unless there is a killer feature in portmaster i don't see a
reason to switch.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: What about creating an office team

[Tilman Keskinöz]

On 07/15/2011 04:51 PM, Baptiste Daroussin wrote:
> On Fri, 15 Jul 2011 16:22:52 +0200, Olivier Duchateau wrote:
>> And about editors/abiword ? even if this port is outdated, it can be
>> added I think.
>>

> sure it also could be a good candidate.

I don't think it is practical to throw office suites of different origin
into one pool. Normally people use only one office suite out of this
list and don't know much about the other.

But if it is libreoffice ports, dependencies and related ports, it could
work.

___
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: cvs commit: ports/accessibility/kdeaccessibility Makefile ports/arabic/kde3-i18n Makefile ports/arabic/koffice-i18n Makefile ports/audio/arts Makefile ports/audio/juk Makefile ports/audio/mpeglib_

[Tilman Keskinöz]

On Jul 7, 2011, at 21:13 , Max Brazhnikov wrote:

> On Thu, 07 Jul 2011 11:09:37 -0700, Doug Barton wrote:
>> On 07/07/2011 10:21, Max Brazhnikov wrote:
>>> Reset maintainership de jure. In fact KDE 3 has not been maintained by
>>> our team
>>> 
>>>  for a long time, not to mention upstream.
>>> 
>>>  Discussed a while ago among the KDE/FreeBSD team.
>> 
>> Certainly if the ports are not being maintained by kde@ then dropping
>> maintainership is the right solution. However given the situation
>> wouldn't deprecation+expiry be the logical next step?
> 
> Until ports are not broken or/and forbidden I see no reason for deprecation 
> and removing them.

Another reason to start the deprecation would be, that they are in the way
of KDE4.

So i think it is desirable to start deprecation. 

But last time i asked on this list a few months ago, there where still several
users raising their interest, so maybe someone of them will step up in the next
days.___
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 Infrastructure Changes

[Tilman Keskinöz]

On 03/19/2011 11:52 PM, Zhihao Yuan wrote:

C/S model can not
clarify the developing web technology these years.


+1
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [ECFT] drm/dri/mesa/xorg-server update [Part 1]

[Tilman Keskinöz]

On Mar 13, 2011, at 18:40 , Martin Wilke wrote:
> 
>> Hi List,
>> 
>> I can confirm that the patch fixes compilation.
>> 
>> The server starts up, but after the KDE4 splashscreen it segfaults.
>> 
>> I tried removing the dri modules from my config, but it does not work.
>> 
>> 
>> I tried to start with an autogenerated config, but the autogenerated
>> config doesn't work either (on Ctrl+C the Server aborts).
>> 
>> 
> ok this is with intel ?

Yes, with Intel. The card is an Intel G33.
The crash is probably happening the first time something tries to access
dri, libdrm.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [ECFT] drm/dri/mesa/xorg-server update [Part 1]

[Tilman Keskinöz]

Hi List,

I can confirm that the patch fixes compilation.

The server starts up, but after the KDE4 splashscreen it segfaults.

I tried removing the dri modules from my config, but it does not work.


I tried to start with an autogenerated config, but the autogenerated
config doesn't work either (on Ctrl+C the Server aborts).


On Mar 12, 2011, at 17:21 , George Liaskos wrote:

> I compiled the intel driver with the following patch:
> 
> --- src/i830_video.c.orig 2011-03-12 18:00:01.0 +0200
> +++ src/i830_video.c  2011-03-12 17:59:08.0 +0200
> @@ -2164,7 +2164,7 @@
> static void
> i830_fill_colorkey (ScreenPtr pScreen, uint32_t key, RegionPtr clipboxes)
> {
> -   DrawablePtr root = &WindowTable[pScreen->myNum]->drawable;
> +   DrawablePtr root = pScreen->root->drawable.id;
>XID   pval[2];
>BoxPtr  pbox = REGION_RECTS(clipboxes);
>int   i, nbox = REGION_NUM_RECTS(clipboxes);
> @@ -2176,7 +2176,7 @@
>gc = GetScratchGC(root->depth, pScreen);
>pval[0] = key;
>pval[1] = IncludeInferiors;
> -   (void) ChangeGC(gc, GCForeground|GCSubwindowMode, pval);
> +   dixChangeGC(NullClient, gc, GCForeground|GCSubwindowMode, NULL);  
>ValidateGC(root, gc);
> 
>rects = xalloc (nbox * sizeof(xRectangle));
> 
> It works but it doesn't support dri1,
> http://cgit.freedesktop.org/mesa/mesa/commit/?id=48c0ff14240044935049a1114edfc69bc6682b95
> 
> Log: http://pastebin.com/W1iiDvWX
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-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: KDE3?

[Tilman Keskinöz]

On 03/02/2011 05:26 PM, Heino Tiedemann wrote:

is KDE3 "out"?


 - misc/kdeutils3 (marked as IGNORE)

or will it be compilable soon?



Is there actually still interest in KDE3?

How about starting the removal of the coredesktop?
___
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: connect to VPN server with l2tp

[Tilman Keskinöz]

On Jan 10, 2011, at 07:49 , Gholam Mostafa Faridi wrote:

> I use FreeBSD AMD64 with Gnome , my friend manage VPN on FreeBSD box and it 
> use L2tp method.
> So my friend say when I want use it , I must use it with l2tp method or way ,
> I search google and I see I can use l2tp for connect to VPN or MPD.
> So for connect to server what I must do ?
> Do I need I run IPSEC on my system or no ?
> Do I need config l2tp ?
> my friend only give me username and password and IP of server and say I can 
> use these for connect server
> 

Hello,

Additional, if it is a commercial vpn-server security/vpnc might be your choice.

It is probably best to ask your friend how it is supposed to 
work___
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: legacy code in bsd.ports.mk

[Tilman Keskinöz]

On 10/23/2010 03:55 AM, Eitan Adler wrote:
> I was going through bsd.port.mk to learn how the ports system works.
> It seems quite complex - partly due to all the different
> configurations that need to be supported.
>

bsd.port.mk is maintained by the portmgr group.
File a PR with your patches and it will be assigned to them.

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