This is mainly for stuff like puppyscripts grafburn pfind etc... at the moment but may eventually and hopefully contain scripts to build puppy completely and automatically using either T2 or slackware as a base. This is not for uploading binary packages only source.

thoughts/comments welcome since that is kinda the whole point of this post.

also my internet connectivity is limited for this week next week back to normal

Edit: you must be registered on sourceforge.net first then pm me your unix name

Maybe I've become a member of the group because I already have an account at sourceforge and I visited the URL earlier.

I wonder if simply having a sourceforge account will enable one to join. Do people have to first PM you with their sourceforge username?_________________Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).

this is a great idea, and I'm slightly amazed that no-one in the Puppy community thought of it before ... a single, secure public repository of source code for non-BK stuff that's currently lying about in dozens (?hundreds) of forum posts and various servers worldwide would be wonderful.

Somewhere in the archives is the story of how Puppy (from the start) was going to be hosted on Sourceforge.
. . . only they did not think it was opensource or even Linux come to that . . . .
So they refused to host Puppy. Who remembers the story?
. . . we got there eventually. Thanks guys

We are Puppy. Resistance is futile. Prepare to be assimilated._________________YinYana AI Buddhism

Yeah, I was the one who originally applied to sourceforge. What happened was someone from sourceforge replied asking for more details about the uniqueness of Puppy, but I didnt read my emails until about 2 days after that email and in the meantime someone else from sourceforge sent a very short email that as I had not responded to their query that were rejecting my application.
Anyway, I sent in a more detailed explanation, but it was ignored.

So that's great, as you now have sourceforge as a repo, that means perhaps I'll just keep my own ibiblio.org account for my planned future puplet. Ibiblio do mirror sourceforge, so you will be getting hosting with them anyway.

Note, I do have Puppy listed at freshmeat. I think they can also do hosting, but I never followed up on that._________________http://bkhome.org/news/

I was very specific that this repo was for the "puppy build system" and other puppy scripts which is exactly what it is ... they also asked some pretty specific questions which i will upload my answers to when i get a chance

also I am having trouble using SVN I have never set one up myself but have checked out of them many times... which is pretty easy would somebody mind explaining how to get this going I mean im sure i can figure it out eventually but help is apreciated

another thing i and the other people so far should be able to log in to the command shell for the repo (this is where i was attempting to add some directories to the SVN as a proof of concept you just login to it with ssh or putty on windows/wine)

the directory structure i propose is this /puppylinux/pupapps/majorversion/minorversion

like this /puppylinux/pupapps/3/1 whould be an app that works perfectly on puppylinux 3.1

So.... what is it? What's it do? Why do we need it? How will we use it?

Would I be right in thinking it can support multiple projects, so that I could (for example) have a section in the svn for Pebble, with download links for the various versions and nightlies, and BruceB could have one for an especially ram-oriented Puppy?

Is this something we'd also want to use for storing the unleashed tree? Or would that be too massive (think 500 MB to start, and more as files get modified into newer versions)). Maybe just for particular packages that require substantial Puppy-mods (0rootfs_skeleton in particular, but also all those p* packages and maybe rox)?

How much overall space do we get? What about per project? How many projects can it handle? Or is it a "just don't do anything excessive, and we won't give you hard limits" type deal? Prove your worth and you get as much as you need?

Sorry for all the questions. I've never used Sourceforge before (other than downloading stuff), or even SVN at all (though SVN has been on my to-do list, as I suspect it will make my life much easier if I want to make a very large project on my own or collaborate on anything but a minor project)._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

The essential content should be sources, and binaries/build trees should be extra.

I guess the problem at the moment is coming up with a simple but functional structure for the project repository. Pizzasgood's ideas about this will be a big help as he has a good understanding of Puppy's core._________________Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).

Okay then. I downloaded and installed the latest SVN on my machine last night so I could play around with it. Meant to do this sooner, but I had some other things I needed to take care of first. Anyways, SVN is a little different from what I'm used to, but I think that if used properly it will be very useful.

Distributions: software and Operating System distributions will generally not be accepted for hosting on SourceForge.net. These project types duplicate content that is available elsewhere and use massive amounts of resources. We will host them if an alternate host can be found for the project content (SourceForge.net services can be used for bug tracking, mailing lists, web site, etc.; File releases should be hosted elsewhere).

Frankly, I don't blame them. We're talking about 700 MB just to start, and it will only grow from there. No I'm not kidding, the extracted unleashed tree has over 600 MB worth of packages, and 50-70 MB worth of drivers, firmware, and other kernel-related stuff.

My firm belief is that we need a server where we can run SVN or GIT or some other system, with the entire unleashed tree (but split in two - the packages would not be inside the unleashed-core area, or checking out unleashed-core would be a pain). This way everything is together. We can fix bugs, branch a package and do major changes and merge it back in, branch off the entire tree to make a custom version, etc. When we're ready for a release, we'd tag that revision as version X.X, and then just continue on our merry way, fixing bugs. If people want the bug fixes they can grab them from SVN fairly easily (we'd want to have it world-readable, just not world-writable). Otherwise they can wait until the next version, or possibly a revised edition. In fact, I imagine it wouldn't be hard to grab just the changes, put them into a .pet or .pup, and upload it as a service package.

Anyways, I just don't think SF is going to cut it for us, in this respect. What I do think SF will be good for is for those packages that have not yet been accepted into the official Puppy tree. (Which I think is what cb88 was thinking.) Things like Pebble, if I wished to put that online (I don't ATM, but if I ever take it to version 2.0 I probably will). That way group projects could work more easily, people can check eachother's code, etc. If a project is eventually accepted into official Puppydom, it could simply be dumped out of SF's SVN and imported into the Official Puppy SVN. If I understand things correctly, this should also preserve the package's history from the SF SVN.

I think that would work out pretty well. It would help keep the official repo clean, while giving the in-development stuff a place to be worked on. For the people actually developing it, the transition would just mean adjusting some of the paths they use. Nothing major.

So, if I understand things right, we need to start figuring out where to put this official Puppy revision-control-server. We also need to weigh the pros and cons and decide what revision-control-software to use. So far SVN looks pretty good, but that's the only one I know anything about. I know that the Kernel is done with GIT. What benifits does GIT have over SVN? These are things we need to look into. I would go do that now, but I have other stuff I need to do. Maybe later tonight or tomorrow I'll see what GIT is all about.

We're also going to need to work out who will have access, who will decide who has access, etc. That is the part that will become hairy. _________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum