Date: Sat, 15 Nov 2014 14:42:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193135] [NEW PORT] www/seahub: Seafile web server front end Message-ID: <bug-193135-13-TXzUqOnc7A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193135-13@https.bugs.freebsd.org/bugzilla/> References: <bug-193135-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193135 --- Comment #30 from Jingfeng Yan <yan_jingfeng@yahoo.com> --- (In reply to John Marino from comment #29) > (In reply to Jingfeng Yan from comment #28) > > Holy C... The test can not access WWW network?! > > Poudriere only allows network access at the fetch phase. A port should > never use the network after that. Then, I have very limited choice, which does not do anything for django related dependency, and as the Seahub release way, leave this part to the users. Or, I have to fight hard to say something like this: Why reviewboard-1.7.22 requires djblets, then it get a specific version of djblets. If other application needs other version of djblets, why we can not have a version of djblets for that app? You can also check: There is no one use py27-django-pipeline 1.3+, but only review board use another version: py27-django-pipeline12. That is why I am confused what is the policy for python pkg version port in FreeBSD port system. Do I miss any important point from the other thread. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193135-13-TXzUqOnc7A>