-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup of the root directory of the source code #133
Comments
Most files are used for building a version of tribler. FFMpeg is used to determine the bitrate while streaming, we can move it somewhere else if neccesary. |
what about a scripts/ dir? |
A "build-scripts" dir sounds like the natural place for all this. Tribler/utilities and Tribler/Tools are already confusing, hence my "build-scripts" proposal. |
Concerning the cleanup, maybe we can restructure the complete souce code instead. Inside Core, all functionality which can be turned on/off with LaunchManyCore should be moved:
Removed:
|
security wise it would be nice to have an up to date build of the ffmpeg executable too instead of having the windows exe laying there. |
And now that we are at it, we could lowercase all the package names. |
If we move Main/tribler.py (and other used entry python files) into the root directory we would not have to set pythonpath to the current directory (since python sets the cwd to the directory of its entry file, or something along those lines). I see several things in 'Main', roughly: entry python files, GUI, and build scripts. Can we either choose a more descriptive name to replace 'Main' or move these three distinct things to the same directory level as Core, i.e. remove the 'Main' entirely. And where would SwiftEngine go in the proposed directory structure? I assume into Core? |
I wouldn't go as far as splitting up the Main folder. However, moving the build scripts to as a toplevel directory makes sense. As for swift, i'm not so sure. Its more an external reference. You don't need the sources of swift to run tribler, you only need a compiled version of swift. Dispersy is a bit different, you actually need the sources in order to run tribler. Maybe Elric has some idea's about it? |
I would keep both references as they are, it makes it easier for us to control which combination of versions of the code should be used in each branch of Tribler. Also, we have to take into account that this refactor will break everything. Including unit tests, build scripts, jenkins jobs/experiments... |
So I removed some parts of code which wasn't used by Tribler anymore. Also some files from the root were removed. However, I think we need to move the reset_.bat files to a tools directory, and move the makedist_ files to some build dir. |
I've reorganized all the mac and windows build/utility scripts and merged the mac and linux shell scripts used to run the devel version into a single one. |
I'll test a devel build on the testmac tomorrow and let you know.
|
I guess this can be considered done, @LipuFei you have been testing the mac build lately, right? |
Problem: too much clutter
keep in root: README.md (and Tribler plus Debian subdirs obviously)
Possible to move .gitignore to both subdirs Tribler and Debian?
Tribler/utilities and Tribler/Tools are confusing.
Perhaps create a cmdline-tools dir and move a lot there?
move all the following root files to a proper subdir:
clean.bat
dispersy-test
dprint.conf
ffmpeg.exe
ldecoder.py
lencoder.py
lucid-xpicreate.sh
makedist.bat
makedistmac.sh
playmakedist.bat
pluginmakedist.bat
pluginmakedist_FX_only.bat
pluginmakedist_IE_only.bat
reset.bat
reset-keepid.bat
runmac.command
swifttest.py
tribler.sh (seems for OSX only?)
vlc-1.0.5-swarmplugin-switch-kcc-src-aug2010-renum110-r16968.patch
xie8transmakedist.bat
xpitransmakedeb.sh
xpitransmakedist.bat
xpitransmakedistmac.sh
xpitransmakedist.sh
The text was updated successfully, but these errors were encountered: