Re: [ros-dev] Package Manager

[Steven Edwards]

--- 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/

[Jonathan Wilson]

>   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. 
I think
that we should also support "plain old zip files" as a package type 
(or a zip file with a little info about what to do). A large number of FOSS 
software packages dont need an installer at all, if all you have to do to 
get it to work is "unzip it into a folder", an installer is overkill.

[Maarten Bosma]

Hi

Steven Edwards wrote:
>   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. 
I don't think that ReactOs nor it's package manager are important enough 
to tell people how to package their programs. So i still think that a 
little script for each package is the best way to handle it.

Jonathan Wilson wrote:
>   I think that we should also support "plain old
> zip files" as a package 
>  type (or a zip file with a little info about what to do). A large number 
>  of FOSS software packages dont need an installer at all, if all you have 
>  to do to get it to work is "unzip it into a folder", an installer is 
>  overkill. 
That's what I'm currently working on. (unzipping)

So would you agree to put it on the svn-server or not ? In addition to 
the program itself there are this 3 things that had to be hosted in a 
new branch:

1. The program downloads tree.xml where all program are listed.
2. A detailed description with all informations e.g. vendor, license ... 
3. The install script. With all informations of how to get and install 
package.


Maarten Bosma

[Casper Hornstrup]

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of
> Maarten Bosma
>  Sent: 2. april 2005 11:47
>  To: ReactOS Development List
>  Subject: Re: [ros-dev] Package Manager
>  
>  Hi
>  
>  So would you agree to put it on the svn-server or not ? In addition to
>  the program itself there are this 3 things that had to be hosted in a
>  new branch:
>  
>  1. The program downloads tree.xml where all program are listed.
>  2. A detailed description with all informations e.g. vendor, license ...
>  3. The install script. With all informations of how to get and install
>  package. 
I don't mind as long as it is at this level (ie. not in trunk/reactos/):
http://svn.reactos.com/viewcvs/trunk/

Be careful with the word branch. Branches are directories with special
meaning in Subversion. What you need is to import the package manager
sources to a directory within trunk. Then, if you wish to work on a
branch, you copy trunk to branches/<branchname>.

Casper

[Maarten Bosma]

Casper Hornstrup wrote:
>   I don't mind as long as it is at this level (ie.
> not in trunk/reactos/):
>  http://svn.reactos.com/viewcvs/trunk/
>  
>  Be careful with the word branch. Branches are directories with special
>  meaning in Subversion. What you need is to import the package manager
>  sources to a directory within trunk. Then, if you wish to work on a
>  branch, you copy trunk to branches/<branchname>. 
Okay thank you, but I still have a question: where should the actual 
package manager sources go to ? To reactos/subsys/system/packagemgr and 
reactos/lib/package ?


Maarten Bosma

[Maarten Bosma]

Hi

Steven Edwards wrote:
>   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. 
I don't think that ReactOs nor it's package manager are important enough 
to tell people how to package their programs. So i still think that a 
little script for each package is the best way to handle it.

Jonathan Wilson wrote:
>   I think that we should also support "plain old
> zip files" as a package
>  type (or a zip file with a little info about what to do). A large number
>  of FOSS software packages dont need an installer at all, if all you have
>  to do to get it to work is "unzip it into a folder", an installer is
>  overkill. 
That's what I'm currently working on. (unzipping)

So would you agree to put it on the svn-server or not ? In addition to 
the program itself there are this 3 things that had to be hosted in a 
new branch:

1. The program downloads tree.xml where all program are listed.
2. A detailed description with all informations e.g. vendor, license ... 
3. The install script. With all informations of how to get and install 
package.


Maarten Bosma