https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193316
--- Comment #32 from Jingfeng Yan <yan_jingf...@yahoo.com> --- (In reply to John Marino from comment #31) > (In reply to chris.dukes.aix from comment #29) > > And to repeat my earlier statement. > > You need Djblets. > > You do not need Djblets packaged for FreeBSD. > > If djblets-06 is needed for seahub in FreeBSD (which can't be committed > until this is sorted) it has to be ports in FreeBSD. The exception is if > seahub adds djblets-06 as one if its distfiles and builds it in the workdir > at the same time as seahub. Maybe this is what you mean by "virtualenv", > but this virtualenv has to work within ports without using the network > during the build phase. > > > > If not... your back to learning about packaging dependencies and best > > practices for an app framework... or hiring someone to do the work. > > Not me. I just commit ports to the tree when its ready. I just wanted > python@ to say the *legacy* port should or should not be in the tree. Hehe, I know it is not "you" (Marino). Never take it personally. Otherwise, I will feel that I am the nut. :) Some wording sounds not very friendly. I have finished using other way to install all the python dependencies. The virtualenv idea is right direction, but it is heavy-weight, and seahub release directory layout could be change a lot. So, I twist the seahub Makefile by borrowing the idea of virtualenv. So, we don't need this this port any more. I will try to close this issue. If I can not, could anyone help to close it. Thanks to all the reviewers for your efforts and suggestion. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
