Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Nov 2014 17:00:37 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 193316] [NEW PORT]: www/py-djblets06: Legacy version of py-djblets
Message-ID:  <bug-193316-21822-wQCzcFiCnT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193316-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-193316-21822@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=193316

--- Comment #30 from Jingfeng Yan <yan_jingfeng@yahoo.com> ---
(In reply to chris.dukes.aix from comment #29)
> (In reply to John Marino from comment #28)
> > I don't know anything about python (and I kind of like that way), but Chris
> > Dukes seems to be saying it's optional and recommends not using it.
> 
> You don't need to know squat about python.  You do need to know the basics
> of package depdencies and the best practices of deploying python
> applications with dependencies that are not met by the packages provided by
> the operating system.
> As of the last time I updated my ports tree, seahub was not in it.
> *IF* it was, I'd suggest you chat with the port maintainer for it.
> 
> The basics.
> You need djblets.
> You do not need a FreeBSD package for djblets.
> 
> Typical behavior for deploying a python based web stack is to use
> 'virtualenv' to create an area for all/most of the dependencies that does
> not change the python modules installed system wide.
> Take a read through https://virtualenv.pypa.io/en/latest/ and
> http://virtualenvwrapper.readthedocs.org/en/latest/
> They are in ports as devel/py-virtualenv and devel./py-virtualenvwrapper
> 
> In addition a web stack usually makes use of something like a Makefile or a
> pip requirement file.  Read more about a pip requirements file at
> https://pip.readthedocs.org/en/1.1/requirements.html.
> 
> 
> Looking at 
> https://github.com/haiwen/seahub
> The author did include a requirements file for pip.
> Unfortunately the 
> Djblets==0.6.14
> requirement does not reference something that is in the index pip searches
> by default.
> 
> My suggestion on your next steps are
> 1) Request that this bug be closed.  You do not need Djblets packaged for
> FreeBSD.
> 2) Work out how to create a virtualenv and activate it.  
> 3) Use pip and the requirements file to install most of the packages in the
> virutalenv.  You may need to comment out the Djblets line.
> 4) Scour the web for the downloads for Djblets, download the version
> indicated in the requirements file and follow the instructions for building
> that manually.  You'll do that in the virtualenv as well.
> 
> When you find the seahub requirementsfile is wrong... take that discussion
> up with the seahub developer.
> 
> 
> As it stands, this port of Djblets exists as a convenience for the
> maintainer of the www/reviewboard package.  If you can use it as is, great. 
> If not... your back to learning about packaging dependencies and best
> practices for an app framework... or hiring someone to do the work.
> 
> 
> > 
> > Assuming that's what he actually said, then I don't understand Jingfeng
> > Yan's next comment.
> > 
> > For my part, I am only concerned about bug 193135 which is blocked by this. 
> > If we can build seahub without  djbets altogether, that sounds good to me.
> 
> And to repeat my earlier statement.
> You need Djblets.
> You do not need Djblets packaged for FreeBSD.
> This port of Djblets exists to support www/reviewboard.

Okay.  I will see how I can change seahub to make it fit it.  AS LONG AS it is
clarified that FreeBSD port system does not want to carries the duplication of
PyPI, I will treat those existing freebsd pkgs with multiple versions as
EXCEPTIONS. :)  If they ARE, we will try not to fall in those category. 

One question,  do all the files that are installed into virtualenv pointed
directory need to be tracked from freebsd port/pkg system?

-- 
You are receiving this mail because:
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193316-21822-wQCzcFiCnT>