Problem with py36 "opt-1.pyc" files
There is an issue in the current (2018.3.0_1) sysutils/py-salt, specific to
py36. The "cpython-36.opt-1.pyc" files included in the pkg seem to contain
pre-patched files.
Any more experienced porters want to offer advice on how to fix this in the
port?
reproduce:
1. install py36-salt (>=2018.3.0)
2. start master/minion
3. error (/var/log/salt/{master,minion}
fix:
1. rm
/usr/local/lib/python3.6/site-packages/salt/grains/__pycache__/marathon.cpython-36.opt-1.pyc
/usr/local/lib/python3.6/site-packages/salt/grains/__pycache__/fx2.cpython-36.opt-1.pyc
I've never seen this before.
Cheers,
Christer
___
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"
preinst_fs_violation - sysutils/py-salt
I've been maintaining a port for some time, but with a recent update of poudriere I'm now getting the following error when building: >> Filesystem touched before install: root/.python-eggs extra >> Error: Build failed in phase: preinst_fs_violation Can anyone suggest what needs to be updated in order to properly build the sysutils/py-salt port? Cheers ___ 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: Any plans to update salt to 0.9.5?
On Sat, Jan 21, 2012 at 12:42 PM, Ruslan Mahmatkhanov wrote: > JFYI. There is 0.9.6 already. The core Salt team is in LA at SCaLE this weekend and getting a lot of attention. We rolled 0.9.6 last night in the hotel lobby, but I've been so busy with conference stuff I haven't updated the port yet, but it's on my list. When I get a little more downtime I'll finish the port update. I did apply the patch Doug submitted (thank you). It won't be much longer before the rest is done.. Glad to see there is more interest here too. Christer ___ 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: Any plans to update salt to 0.9.5?
On Thu, Jan 19, 2012 at 8:12 PM, Doug Barton wrote: > I've been evaluating salt, and would prefer not to deploy prior to the > msgpack update in 0.9.5. I am hoping to get the port updated today, yes. Thanks for the additional nudge to get it finished :) christer ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 8:09 AM, Greg Larkin wrote: > You get the award for persistence, so pat yourself on the back! That's one way to look at it :) So, I've been double-validating every aspect of this port as I want to make sure it's 100% before I submit it, and I ran into one more issue. I'm using a files/patch-setup.py to tweak the upstream setup.py to match port standards. The one thing it is not doing is installing the configuration (data_files) as ".sample". I did some digging and the Python documentation says that the setup.py can not rename data_files when it installs them[1]. Did I screw up the patch, or is there a different way it should be done? I get this error when building the port: running install_data error: can't copy 'conf/master.sample': doesn't exist or not a regular file *** Error code 1 This is a pastebin of my patch-setup.py: http://pastebin.com/3ezTBdy9 Thanks again everybody. [1]: http://docs.python.org/distutils/setupscript.html#installing-additional-files ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:51 AM, Doug Barton wrote: > On 12/22/2011 23:47, Christer Edwards wrote: >> The pid file does not seem to get created. > > Ok, so fix it. :) Setting 'pidfile' in the rc.d script is only useful > if the service creates a pid file. It's not magic. > > Given that the thing seems to create a lot of instances of itself, and > one pid may not be enough, you might want to try commenting out the > pidfile in the script and see if that works. /facepalm - that works. Now that I feel adequately defeated by something so simple, I'm going to bed :) Thanks again for all the help. ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:43 AM, Doug Barton wrote: > On 12/22/2011 23:40, Christer Edwards wrote: >> On Fri, Dec 23, 2011 at 12:32 AM, Doug Barton wrote: >>> So now do 'ps axww | grep salt' and confirm that it's really running >>> with python2.7, as opposed to something different. >> >> Indeed it is running with python2.7 > > Ok, does the pid file exist? Does it have the correct information? The pid file does not seem to get created. See this output.. [root@salt /usr/local/etc/rc.d]# ls -hal /var/run/salt* ls: /var/run/salt*: No such file or directory [root@salt /usr/local/etc/rc.d]# ./salt_master start Starting salt_master. [root@salt /usr/local/etc/rc.d]# ls -hal /var/run/salt* ls: /var/run/salt*: No such file or directory [root@salt /usr/local/etc/rc.d]# ps axww | grep salt 13130 ?? SJ 0:00.10 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13131 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13132 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13133 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13134 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13135 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13136 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13137 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:32 AM, Doug Barton wrote: > So now do 'ps axww | grep salt' and confirm that it's really running > with python2.7, as opposed to something different. Indeed it is running with python2.7 Here is some ps output before and after starting the rc script: http://pastebin.com/raw.php?i=d86Mgq3N ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:11 AM, Doug Barton wrote: > Did you read the pre-commit checklist? Particularly item 7? "If the script uses an interpreted language like perl, python, or ruby, make certain that command_interpreter is set appropriately." Each rc script includes: 'command_interpreter="%%PYTHON_CMD%%"' as suggested earlier. I looked at another port (security/denyhosts) and noticed it used "%%PYTHON%%" vs "%%PYTHON_CMD%%", but either way after installation it expands properly to "/usr/local/bin/python2.7" as I would expect.. Again, the error I'm finding is: [root@salt /usr/local/etc/rc.d]# ./salt_master start Starting salt_master. [root@salt /usr/local/etc/rc.d]# ./salt_master stop salt_master not running? (check /var/run/salt_master.pid). ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Thu, Dec 22, 2011 at 8:12 PM, Doug Barton wrote: > You need to pay attention to what Greg told you, and read the Handbook > page that I sent. :) OK. I give. I've read that Handbook page a number of times and nothing is jumping out at me. I've been tinkering and testing all evening and I'm just not getting it to work. I'd really like to know what I'm missing. I feel like it's going to be really obvious once someone points it out, but until then.. I'm just not seeing it. The archive below is what I currently have.. http://dl.dropbox.com/u/312414/salt-port-2011-12-23.tar.gz Christer ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Thu, Dec 22, 2011 at 7:01 PM, Doug Barton wrote: > Try doing s/-/_/ for all the $name variables. I think that's what's > causing your problem. I did a little more testing (and I added the Makefile and .in file suggestions). I can now get it to run consistently if I change $name to use all underscores, and also update $command to 'salt-master' instead of $name. Definitely something funny about having dashes in the name I guess. Also, one last thing.. anytime I try to stop the newly started services they each complain about 'salt_master not running? (check /var/run/salt_master.pid).' Do I need to create the pid in the rc script, or in the Makefile? Very, very close now. Thanks again for all the help guys. ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Thu, Dec 22, 2011 at 5:45 PM, Doug Barton wrote: > There are some style problems and one real bug that are repeated for all > 3 scripts. I attached a fixed version of one of them, hopefully that > will help you see what's needed to fix the other 2. Also, please review > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html, > especially the pre-commit checklist. I made the changes you suggested and tried a fresh build of the port inside of a jail. Below is a pastebin of trying to start the service(s) just after installation. http://pastebin.com/raw.php?i=2wGBk0PY 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: RUN_DEPENDS for python based port
On Thu, Dec 22, 2011 at 1:52 PM, Christer Edwards wrote: > At this point I believe all I have left is to write init scripts for > the minion and master and it should be ready to go. That reminds me, > what method should I use to include a short message on getting things > running post installation? ie; cp the .sample files into place and > update rc.conf, etc. I must have horrible luck or something, but I've put together rc scripts and they don't work. This port sure is giving me a hard time! Here is a link to the updated archive with the .sample suggestions applied as well as the rc scripts. Can anyone see what is wrong with them? I simply get complains that it isn't toggled to YES in the rc.conf, but it is.. http://dl.dropbox.com/u/312414/salt-port-2011-12-22.tar.gz Thanks again ___ 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: RUN_DEPENDS for python based port
On Thu, Dec 22, 2011 at 1:31 PM, Ruslan Mahmatkhanov wrote: > Btw, i'd prefer to patch setup.py once again to install them with > '.sample' postfix. User will need to copy them into just `master' and > `minion' to make it work. This will guarantee that user will not lost > their configuration while upgrading salt to new version from ports. I've updated this in the patch-setup.py and the pkg-plist as suggested. This is starting to really come together, thank you! At this point I believe all I have left is to write init scripts for the minion and master and it should be ready to go. That reminds me, what method should I use to include a short message on getting things running post installation? ie; cp the .sample files into place and update rc.conf, etc. Thanks again for all the help! Christer ___ 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: RUN_DEPENDS for python based port
On Thu, Dec 22, 2011 at 2:43 AM, Ruslan Mahmatkhanov wrote: > Sorry for delay. Please review this patch: > http://people.freebsd.org/~rm/salt.diff.txt > > it fixes: > - fetch (FETCH_ARGS added, that i noted erlier) > - build (you mistyped py-Jinja2 dependency) > - python version changed to 2.6-2.7 > - whitespace issue (spotted by portlint) > - man-pages install > - configuration files install > - missing files in pkg-plist Wow. Thank you for those fixes! Everything seems to build correctly for me now, but I'm wondering if I didn't apply the setup.py patch properly because I'm still not getting the config files. Do you think you could tell me how setup.py patch is supposed to be used from files/? 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: RUN_DEPENDS for python based port
On Sun, Dec 18, 2011 at 8:22 PM, Ruslan Mahmatkhanov wrote: > Looks like mailing list eats the attachment. Would you please upload > it somewhere and provide us with the link. Apologies. I've uploaded the archive here: http://dl.dropbox.com/u/312414/salt-port.tar.gz ___ 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"
help with man pages
The port I'm working on includes about a half-dozen man pages which I
understand I need to use MANn to install. What I guess I don't fully
understand is how to path those files. If the files are found in the
extracted source under source-version/doc/man/ should I use:
MAN1= doc/man/manpage.1
MAN7= doc/man/manpage.7
...etc...
or do I need to reference ${WORKSRC}/doc/man/ ?
Do I also need to install the man pages in do-install?
${INSTALL_MAN} ${WRKSRC}/doc/man/manpage.1 ${PREFIX}/man/man1
Appreciate the help
Christer
___
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: RUN_DEPENDS for python based port
On Sat, Dec 17, 2011 at 3:23 AM, Ruslan Mahmatkhanov wrote:
> Chris and Matthew already noted what the problems are.
> I also suggest to use:
>
> ${PYTHON_PKGNAMEPREFIX}yaml>=0:${PORTSDIR}/devel/py-yaml
That is much cleaner. Thank you.
> So USE_PYTHON=yes should be changed with USE_PYTHON= 2.6-2.7, (otherwise
> port build will fail with python3) and LICENSE= ASL worth to be added.
Also added.
I've attached an archive including all the port files (distinfo,
pkg-plist, etc) for any other feedback you can offer. I still have two
remaining issues on my checklist that perhaps the group can provide
solutions for as well.
1) Building the port never successfully fetches the upstream .tar.gz,
but if I copy/paste the URL and run fetch manually it works just fine.
Thoughts?
2) The existing setup.py installs the two config files
(etc/salt/{master,minion}) to /usr/etc instead of /usr/local/etc. I'm
not familiar enough with setup.py to tweak that. Any suggestions
there?
If I can get those last few things figured out I'll submit the port.
Thanks,
Christer
___
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"
RUN_DEPENDS for python based port
I've been working on building my first python based port recently and
I'm running into some issue that I'm hoping the list can provide some
tips for. Currently the Makefile looks like this:
-
# New ports collection makefile for: salt
# Date created: 17 Dec 2011
# Whom: cedwards
#
# $FreeBSD$
#
PORTNAME= salt
PORTVERSION=0.9.4
CATEGORIES= sysutils python
MASTER_SITES= https://github.com/downloads/saltstack/salt/
MAINTAINER= christer.edwa...@gmail.com
COMMENT=Central system and configuration manager
LIB_DEPENDS=zmq.1:${PORTSDIR}/devel/zmq
USE_PYTHON= yes
USE_PYDISTUTILS=yes
RUN_DEPENDS+=
${PYTHON_SITELIBDIR}/yaml/__init__.py:${PORTSDIR}/devel/py-yaml \
${PYTHON_SITELIBDIR}/zmq/__init__.py}:${PORTSDIR}/devel/py-pyzmq \
${PYTHON_SITELIBDIR}/Crypto/Cipher/__init__.py:${PORTSDIR}/security/py-pycrypto
\
${PYTHON_SITELIBDIR}/${PYEASYINSTALL_EGG}/jinja2/__init__.py:${PORTSDIR}/devel/py-Jinja2
\
${PYTHON_PKGNAMEPREFIX}M2Crypto>=0:${PORTSDIR}/security/py-m2crypto
.include
-
I'm not sure if I've done the RUN_DEPENDS properly, because when I try
to 'make' the port, it tries running the salt tool and complains about
missing python modules. The modules are of course provided by the
depends, but they don't get installed if they're missing.
I'd really like whatever feedback the list can offer to getting this
ported properly.
Cheers,
Christer
___
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: [request for testers] update devel/ccache to 3.0.1
On Mon, Jul 26, 2010 at 10:42 AM, Emanuel Haupt wrote: > Since this port is used by a large audience, I'd like to ask for > feedback prior to the update. Feedback from people using ccache > integrated in tinderbox (ports-mgmt/tinderbox) is also gratefully > appreciated. I've been using ccache 3.0.1 via this patch on two hosts + jails and I've not had any problems. If there is any particular test cases you'd like run, just let me know. Otherwise, buildworld/kernel is fine. Building ports has been fine, etc. Christer ___ 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 testers: www/shellinabox (Shell in a Box)
On Fri, Jun 25, 2010 at 8:32 AM, Christer Edwards wrote: > top shows shellinabox running > sockstat -4 shows IP:4200 > none of my browsers ever connect.. > I just tried re-installing (after re-downloading your Makefile), and it's working fine for me now. Thank you -- Christer Edwards ___ 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 testers: www/shellinabox (Shell in a Box)
2010/6/25 Vitaly Magerya : > Builds & installs fine. Does not run: > > # /usr/local/etc/rc.d/shellinaboxd onestart > Starting shellinaboxd. > # /usr/local/etc/rc.d/shellinaboxd onestatus > shellinaboxd is not running. > # tail -1 /var/log/messages > Jun 25 11:31:30 vbsd kernel: pid 4461 (shellinaboxd) uid65534: > exited on signal 11 > # shellinaboxd > Segmentation fault > # uname -mrsi > FreeBSD 8.0-RELEASE i386 GENERIC Mine builds and installs fine, and seems to run, but I'm not able to connect to anything.. top shows shellinabox running sockstat -4 shows IP:4200 none of my browsers ever connect.. -- Christer Edwards ___ 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 testers: www/shellinabox (Shell in a Box)
2010/6/24 Olivier Cochard-Labbé : > I've just finished my port of Shell in a Box: It's a secure web server > that provide ajax terminal emulator. > More information on the official website: > http://code.google.com/p/shellinabox/ I'll test it! I've actually had written on my daily todo list "port for shellinabox", and I haven't gotten around to it. I'll let you know what I find out. -- Christer Edwards ___ 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: graphics/libchamplain build failure (libpng.so.5 not found)
On Sat, May 15, 2010 at 4:51 PM, Jason wrote: > I ran into this as well, and after completely removing libchamplain, and > doing a rebuild on all libraries needing png, this port installed with no > issue and built against libpng.so.6, as expected. > I'm having a similar issue, although not with libchamplain. Can you comment regarding how you rebuilt all libraries needing png? I've been trying to force-rebuilds of ports, but I'm still getting complaints for applications needing libpng.so -- Christer Edwards ___ 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: ccache 3.0 port
On Wed, May 12, 2010 at 12:10 AM, Ion-Mihai Tetcu wrote: >> >> To submit an update, generate a diff against the previous version >> >> of the port using 'diff -Nur'. Attach this to a PR 'send-pr -a >> >> port.diff' >> > >> > I prefer http://ionut.tetcu.info/FreeBSD/How-to-submit-a-diff.txt Using these instructions I have generated a CVS diff and submitted it. Is there anything I should do at this point, other than wait for someone to get around to it? Status can be viewed here: http://www.freebsd.org/cgi/query-pr.cgi?pr=146527 -- Christer Edwards ___ 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: ccache 3.0 port
On Tue, May 11, 2010 at 8:31 AM, Sahil Tandon wrote: > Actually, after thinking about this some more, avilla@'s DISTVERSION tweak > is more elegant and gives us the same end result with less fiddling. Stick > with that and sorry for the noise! should I post the current portlint-approved Makefile someplace for further consideration, or should I go about a process of submitting it? If the latter, what is the appropriate way to submit a new/updated port? -- Christer Edwards ___ 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: ccache 3.0 port
On Mon, May 10, 2010 at 8:23 PM, Adam Vande More wrote: >> DISTVERSION= 3.0pre1 >> is shorter and cleaner >> > > That's longer, and cleaner is debatable. Well I've used DISTVERSION and it now reports 'looks fine.' What is the next step? -- Christer Edwards ___ 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: ccache 3.0 port
On Mon, May 10, 2010 at 7:37 PM, Sahil Tandon wrote:
> Regarding portlint's FATAL output, please review Package Naming
> Conventions in the Handbook. Specifically, "If the software version has
> strings like ``alpha'', ``beta'', ``rc'', or ``pre'', take the first
> letter and put it immediately after a period." So you could try
> sometihng like:
>
> PORTVERSION= 3.0.p1
> DISTNAME= ${PORTNAME}-${PORTVERSION:S/.p/pre/}
I have been trying a number of variations as suggested in the
Handbook, but your suggestion worked well. 'portlint -a' now only
warns about there being only one mirror. I will work on resolving that
next.
Thank you,
--
Christer Edwards
___
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"
ccache 3.0 port
As a disclaimer, I don't have much experience maintaining ports. I've altered a few for my own personal use, but never delved too deeply into the "official" details of it all. I have been working with the upstream maintainer of ccache to solve an issue related to ccache and buildworld on amd64. I have built ports on my local machine(s) to use his latest releases (3.0pre0 and 3.0pre1). I would like to create an official port for the newer version once this fix is in place, but I'm running into complaints from portlint that I'm not sure how to address. I am eager to learn and I'm happy to dedicate the time to put this together, if someone doesn't mind offering advice on getting it to pass portlint's critical eye. The upstream download is available here: http://samba.org/ftp/ccache/ My (current) port is available for inspection and feedback here: http://zelut.org/projects/misc/ccache-3.0pre1-port.tar.gz It is based primarily on the current (v2.4) ccache port, minus the patches (which don't seem to be needed). I haven't updated the Maintainer information or any other details so far. Looking forward to feedback, -- Christer Edwards ___ 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"
port request - listadmin (mailman admin utility)
I don't know if this is exactly the right place to ask, but I'd like to request a port. Previously, on debian, I administered a number of mailman lists using a CLI tool "listadmin". After migrating my servers to FreeBSD 7 I'm unable to find that port. http://freshmeat.net/projects/listadmin/ Thank You, Christer pgpLsE1ICwsbK.pgp Description: PGP signature
