Jump to content

T3hGamerDK

Active Members
  • Posts

    11
  • Joined

  • Last visited

About T3hGamerDK

  • Birthday 07/04/1993

Profile Information

  • Gender
    Male
  • Location
    Denmark

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

T3hGamerDK's Achievements

Newbie

Newbie (1/14)

  1. It sounds like the license you want is the BSD 3-clause license: http://www.opensource.org/licenses/BSD-3-Clause
  2. This entire project is now on github @ http://github.com/mastersrp/PyUpdater I know this thread is dead, but any new progress will be listed and uploaded (pushed) to that URL.
  3. I'd say you Learn Python The Hard Way.
  4. When you use this system (MinGW) with the builtin 'terminal', you would actually just call "gcc" or "g++" at it should work without problem.
  5. As long as you follow the standards cross-platform, and the C++ standards (not the Microsoft C++ standards, as they tend to avoid and even depreciate modern standards), then you should really be good to go. In the many years I've been programming C++, I haven't had any issues. I use CMake for my project file generation, and compilation works fine using MinGW and/or MSYS on Windows and GCC on Linux. You *almost* can't go wrong using something like CMake or Premake4.
  6. The most cross platform it'll get is GTK#, unless you write your own.
  7. Holy shit! I had no idea what this program does, but that picture sure caught my attention. Looks very slick, and after reading a bit, is QUITE useful. Thanks! :D
  8. With "tweaking Ubuntu", do you mean starting up programming (since you mentioned C++ and Java) or just changing settings, visuals and things like that?
  9. Been using Linux for quite a while.. Does that count as security? :D Using a non-root account with an alphanumeric password completely random; Social Engineering won't work on this bitch 8)
  10. What are you talking about?
  11. I've been working day-on/day-off on a little project written entirely in Python 3.1 I really liked the way that portage worked in Gentoo, and I had been having issues with keeping my package manager system cross platform (I wrote a simple system in bash). I decided: "Hey, why not try to replicate the way that it works on Gentoo, as a cross-platform system!" And so my journey began.. Although this system isn't as big or as perfect, stable or shiny as Gentoo's, it's certainly heading in the right direction. Currently, it relies entirely on the standard libraries in Python, and works on both Windows and Linux (tested). It consists of several elements, all of which are (somewhat) described in the README.html file. I'm using JSON setting files (.json) instead of XML files, as this is much faster and easier to do. It has a few "modules" which can be run as scripts like "scripts" [OPTIONS] .. [TARGETS] NOTE: So far I don't know how to print with colors on Windows, with the standard library. update.py: For each package downloaded (tar.gz or tar.bz2) a sha1 hash is used and saved as "tarfile".checksum. I'm not using version numbers here, if there's a new version, we pull it. backup.py: There's also clean.py, which'll 'clean up' (wipe) either a selected package, or (if "all" is specified) checksums, working directory, backups and .pyc files) And compile.py, which'll look for either Makefiles or CMakeLists.txt files within' the install directory of the packages. There's still a lot of information missing in the README.html, and several features (hence the WIP tag) It reads packages in the form of: { "name": "DND", "tarfile": "DND.tar.bz2", "instdir": "projects#:ossep#DND", "depend":[ "src#:ossep#lua" ] } The "tarfile" tag is downloaded by adding it to the settings file "mirror" tag (mirror+tarfile), unless the tarfile tag starts with http(s) or ftp. The "instdir" tag is where the project will be extracted to, and the #:ossep# is a variable. Currently it's the only variable supported :P "depend" is dependencies. MUST be another package (minus .json) If the dependencies is NOT installed, it'll be installed. Oh! And I forgot to mention the "installscript" tag! It's only ("officially") used in the src/lua.json (Lua 5.2 alpha sources) package. Install Scripts are just executables being run once everything is extracted. With the Lua package, I'm using it for compiling everything when it's ready, like this: (media tagged for longness) http://dl.dropbox.com/u/5579836/Pic/PyUpdater/PyUpdater_installscript_lua.png Any feedback on this project would be nice :) Here's a link! (Note: This link is ALWAYS the latest version I've uploaded) I decided to write this in Python 3.1 not only because it's cross-platform and easy to use, but also because others can give feedback on it quite fast, and learn from it as well (Although the code isn't well-commented)
×
×
  • Create New...