GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
with regards to python of c++, it really doesnt matter. python is really good stuff, and it might be the easiest way to implement something like this. i have some ideas that i want to discuss with you about what the application will _actually_ do. i figure there will be a few parts to the project, so itll take a while to get it done.
the sourceforge page still isnt up, but it should be up soon. hopefully the OP will post in here once its up. once thats up correspondence will be even easier.
my email should be in my profile for this site. if its not just make a post and ill put it up. microsoft/linux, i doubt this will require _that_ much experience, and either way its a good learning experience.
at this point, im thinking python might be best for this project. ill tell you why once we get more into corresponding and discuss what we want pkgswarm to really be.
nick, i dropped you an email. ms/lin and corbin, you guys may want to email him to or email me (dforsythe<at>gmail<dot>com) so that i can get your email addresses. anyone else interested in this project feel free to email me too.
Could we get it hosted on Google code to start off with, just to get the ball rolling? Base it on the Bittorrent 4.x python code so we don't reinvent the wheel so much?
From 4.4 onward I think, Bittorrent started needing a lot of extras to work, I'm guessing people would look for a light package manager?
Also, change the name to swarmp: SoftWare Automatically Revamped for Many People (I was bored )
Could we get it hosted on Google code to start off with, just to get the ball rolling? Base it on the Bittorrent 4.x python code so we don't reinvent the wheel so much?
From 4.4 onward I think, Bittorrent started needing a lot of extras to work, I'm guessing people would look for a light package manager?
Also, change the name to swarmp: SoftWare Automatically Revamped for Many People (I was bored )
sawwwback: i got your message, but you blocked the email feature for your own account. email me at the address i posted in this thread. we appreciate the help :-)
I don't have that much free time, but I could probably stand to do some less involved things like bug hunting, docs, and the SF website.
I would really like to see this as not an entirely new package manager, but just a layer on top of apt/yum/etc, maybe with a plugin architecture, as there will always be more package managers, and this would allow other people to write plugins for their own. This might mean a lot of initial work before anything usable is produced, seeing as everyone in this thread is on different distros/BSDs (I read your profile, Ha1f ), but people are going to be less wary of picking up a layer on top of their favourite package manager (with all it's features) than an entirely new PM that they might not consider as good, and more popular and well-known the project is, the more people will join in, and the more chance it will have of surviving. Writing a new package manager will also be a lot of work, you should be able to just stand on the shoulders of the existing ones, and if need be, this part can be written later anyway.
I really like the idea of this project and it has the potential to be something big, and I don't want to see it just die. A lot of projects haven't gone into the design phase enough, and just stagnate when the coder/s comes up against a brick wall. A lot of discussion and planning is still needed before anyone even thinks of writing code, so that will give people a chance to research everything involved (Python, daemons, bittorrent, package managers..). Python is a great first language, so you (us) coding newbs can help too.
Disclaimer: As you can read from my sig, I am an idiot. You guys probably know a lot more than me about all this stuff.
If you want to help out, or want to know more about the project, please feel free to email me or anyone else on the project, or join the mailing list. At this point, we only need a few python programmers, but if you join the mailing list, youll be able to help out with docs and bug hunting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.