Jump to content

Recommended Posts

Posted

This is quite an open question. For instance lots of packages on our network are tied to licensed software and thus we couldn't copy them to use elsewhere. In the instance of free software (VLC media player, flash player etc) RM do something they call blueprints to make it easier, see here.

 

I have known schools to share MSIs before though I don't know the legalities of doing that (seeing as Adobe require you to register in order to get their MSIs for example).

Posted

The RM Communities forums (RM Community Page) are usually pretty good if you're after help with packaging something that isn't covered by Blueprints.

 

What open source stuff were you thinking about?

Posted
This is quite an open question. For instance lots of packages on our network are tied to licensed software and thus we couldn't copy them to use elsewhere. In the instance of free software (VLC media player, flash player etc) RM do something they call blueprints to make it easier, see here.

 

I have known schools to share MSIs before though I don't know the legalities of doing that (seeing as Adobe require you to register in order to get their MSIs for example).

 

Depends on the contents of the package and the EULA. Any package you make containing copyrighted material, in general, is not permitted. This is why RM are not allowed to provide CCx packages for things like Flash but can provide the blueprints to turn the software into a CCx package.

 

The RM Communities forums (RM Community Page) are usually pretty good if you're after help with packaging something that isn't covered by Blueprints.

 

Requests for copyrighted material via RM Communities will be moderated ;)

Posted
Openoffice and VLC both have blueprints for them not sure which versions.

 

 

VLC tends to get updated pretty quickly after a release. From what I remember though (would need to check), the package just wraps around the exe and doesn't create any additional MSI, so updating it to work for a new minor release should just be a case of updating the EXE entry in the package info.

 

OpenOffice is still stuck around version 3.0 I believe.

Posted

There's a new Blueprint for Openoffice.org 3.2.1 just appeared in RM's Blueprint RSS feed.

 

When I get back to work after the summer break, I'll have a go at packaging Blender to see how easy it is.

Posted
There's a new Blueprint for Openoffice.org 3.2.1 just appeared in RM's Blueprint RSS feed.

 

When I get back to work after the summer break, I'll have a go at packaging Blender to see how easy it is.

 

That's great.

 

Thanks.

  • 2 weeks later...
Posted

Right, the following is a basic CC3 package structure for Blender 2.49b

 

It's fairly basic so should import into CC4 without any problems (I'm not at a CC4 school until next week so can't test it on CC4 yet)

 

It doesn't do anything fancy with shortcuts, it just installs and uninstalls. Tested only as systemadmin but I can't see anything that would stop a normal user from running it so far.

 

[Package]

ExeFile=blender-2.49b-windows.exe

Version=1.0.0.0

Description=Blender 2.49b

AddCommand= /S

UninstallExeFile=c:\program files\blender foundation\blender\uninstall.exe

UninstallCommand= /S

OS=5.WS

 

 

HTH

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...