--- Richard Campbell <eek2121(a)comcast.net> wrote:
> *faints*
*grabs the smellinbg salts for Richard and waves hi to Phillip.
Phillip, welcome back! I was looking at some of your code a while back (RAM Disk Driver) and was
wondering if we should add support to it to be a general purpose RAM driver while keeping suppport
for loading from bochs images as it does now.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
Hi,
it seems we have now a file en.rc and En.rc. This will not work on windows.
- Hartmut
weiden(a)svn.reactos.com wrote:
>corrected file name so it matches the include in slayer.rc
>
>
>Added files:
>trunk/reactos/lib/shellext/slayer/En.rc
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
On Mar 30, 2005 12:49 PM, James Dodd <admin(a)doddnetwork.co.uk> wrote:
> I think people are right with the about page.
The whitepaper and FAQ will answer more than enough. The entire first
set of links at the top links to various 'about' topics.
> I've also moved the language bar to the top of the screen...
That I like.
> Even these companies are moving away from this and creating a more user
> friendly approach to their sites which intern represents their OS.
Yes, those *companies*. Apache.org seems to be doing fine with their
minimalist design.
> The new site at the moment does seem more appropriate to developers as
> apposed to attracting new audiences.
What new audiences? Developers are really what is most important to
this project right now. I'm going to stop short of chanting
"developers! developers! developers!" ;)
Cheers
Jason
Hi all
Jh sent me a better look: http://reactos.com/newsite/reactos_index.html
I think it looks better!
I've also reworded our slogan at the top to read what Steven suggested.
Magnus: I'm sorry but your critism is not constructive! Which links do
you want on the frontpage that aren't already there? You cannot link
to everything on the frontpage either!
Cheers
Jason
And needs an SVN account ;)
I'm glad to see everyone kept the project going without me, I am
impressed with the progress!
Hopefully now I can get back to contributing.
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> I can think of an infrasturcture where one could update a list and
> gather packageinformation from all over the internet and install random
> apps hosted by theirs creators or sf.net
Yeah thats kinda my thinking. We maintain a database of all of the free Win32 software on
SourceForge and try to get them all to use MSI or NSIS to package them.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Sports - Sign up for Fantasy Baseball.
http://baseball.fantasysports.yahoo.com/
Hi,
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> As you might remember firk85 and me have started coding a package
> manager for ReactOS. More information and a download linkcan be found on
> the wiki on http://wiki.reactos.com/PackageManager .
>
> Since it is now so far that it is at least a bit useful, I'd like to ask
> what you think of adding it to the svn-tree ?
MSI already does everything you want to do. Add support for loading MSI packages by developing
your application on Windows and then it should work in ReactOS as we share msi.dll and msiexec
with wine. Vendors can already use Wix to package thier applications. For bonus points make it tie
in nicely with NSIS.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi,
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> I missed to introduce a concept of the package manager here. Packages
> are not a Archive file with an instruction for installing like apt
> packages. The more an instruction to download the program, that might be
> running the setup with a special parameter or downloading an arrive
> file with the binaries. That is a little bit of BSD ports or Gentoo Emerge.
>
> This is why I think MSI files aren't the right think to replace the
> basic based scripts, that are used at the moment. It simply not what
> they have been made for. But if the vendor of the application provides a
> msi file of cause it can be used; with a "msi"-script-command.
I think the idea of a central repository containting information on Free(Open) Win32 is a good
idea.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi,
--- Jonathan Wilson <jonwil(a)tpgi.com.au> wrote:
> Why not?
> Its perfectly possible to include a CPL program on the same CD or zip file
> as a GPL program as long as they dont directly mix code (IANAL but this is
> what I understand). Linux distributions mix and match code of all different
> licences and get away with it.
Because we have developed this project like Debian or FreeBSD though we have a "Unspoken Social
Contract" GPL incompatible software will not be mixed in the same package or on the same medium as
GPL compatible software. I am perfectly happy to have WiX or any other OSS package shipped with
ReactOS on a Non-Free CD. It does not mean that I view the CPL as Non-Free, far from it, but in
the GPLs current incarnation it has been deamed GPL-incompatible. Maybe the GPL v3 will address
these issues and we can even ship WiX in the same package/cd as ReactOS but I still would rather
not have ReactOS become dependant on code developed by Microsoft as it may make them rethink the
idea of Freeing other packages in the future.
I would rather link, provide downloads to (apart from the main ReactOS package), and ship it on a
"extras" CD.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> If I understood you correctly you said that there is no need for
> developing a compleatly new system, a Packagemanager only had to provide
> a interface for the msi files.
Right, You can interface directly to the MSI database in the registry.
> First of all, I have to say that I don't know much about that msi stuff.
> So my question is how would the msi file and the program communicte ?
> The point with a packagemanager is that you choose to install lots of
> packages and leave your PC alone. So the package manager had to send the
> dessions of the user to the msi file and then the msi file had to do
> it's operations senlitly. And send reports to the package manager from
> time to time. And if something went wrong, it has to send a compleate
> error report.
Well MSI packages have a lot of options, more so than are used by most people. Most people just
write a Install Shield wizard and have the software packaged in a msi but it can do self-repair
and modification and all sorts of cool stuff. Most third partys now ship apps as MSI as its what
Microsoft supports or they use NullSoft Install System so making a easy to use interface to both
of them will win the most support. Its like a mini-sql database so you can even use XML to mess
with it in your Package Manager. If I understand correctly the Microsoft tool for creating MSI
packages "WiX", uses a xml file for input. The only problem is that WiX is CPL and not GPL so we
cannot ship it with ReactOS unless we make it a seperate download.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com