Composer and minified version of Nette

May I then ask how do you guys handle this fact, that you can't get the minified version of nette via composer?

For example on deploy I'd like to replace libraries with their minified versions…

Actually, you CAN download the minified version via Composer. It is important to realize that Composer itself is very often not the limitation, Packagist is. All you need to do is to host your own repository which would contain the minified version.

@David Grudl: I still don't understand why having custom repository hosted at nette.org is a problem (its a one hour work to make it work). I'm actually working on my own composer-repository which should solve current problems with Packagist.

@David Grudl: You are already building packages for download, right? So I'm guessing it would be pretty easy to build few more variants of each package. For example one package with just composer.json & nette.minified.php and another one with normal version of Nette but without sandbox, examples, tests all all the other stuff. Once you have the packages ready you to generate one more file – packages.json which describes which packages are available. And that's it =)

packages.json example

{
	"packages": {
		"nette/nette": {
			"2.0.11": {
				"name": "nette/nette",
				"version": "2.0.11",
				"dist": {
					"url": "https://files.nette.org/Nette-2.0.11.zip",
					"type": "zip"
				}
			}
		},
		"nette/nette-minified": {
			"2.0.11": {
				"name": "nette/nette-minified",
				"version": "2.0.11",
				"dist": {
					"url": "https://files.nette.org/Nette-2.0.11.minified.zip",
					"type": "zip"
				}
			}
		}
	}

}

The only think I'm not sure is how it would handle dev packages.

@enumag: I don't understand. What problem it does not solve?

@David Grudl: I believe this may be possible to solve with

{
	"require": {
		"nette/nette-minified": "2.0.*"
	},
	"require-dev": {
		"nette/nette": "2.0.*"
	}
}

The nette/nette package would have to contain something like

"replace": {
	"nette/nette-minified": "self.version"
}

I haven't try it though, so it may not work at all.

BTW: How did you solve this problem before Composer-age? You need to somehow replace full Nette with minified version during deployment process.

@David Grudl I was curious so I've tried it myself. And it doesn't seem to work. Composer installs both packages ignoring the fact than one replaces another (actually even if you specify them conflicting, Composer will still install both of them [so it is obviously a bug]). The workaround I have found is to have nette/nette-minified as metapackage which requires the actual nette/nette-minified-real. nette/nette then replaces nette/nette-minified-real.

Jan Tvrdík wrote:

@David Grudl I was curious so I've tried it myself. And it doesn't seem to work.

I tried it too, it didn't work.

hrach wrote:

I agree with Jan Tvrdik. From my point of view it's completely unnecessary to have https://github.com/…tte-minified repo. nette.org package (composer) repository should have do the job.

What job?

Switching to minified version should me completely managed by deployment,

Yes, it should, because I absolutely don't need Composer autoloader. But for other Composer users (without RobotLoader) it is real problem.

try “–prefer-dist”

How many libraries you know where this could help?

@hrach: Damn you, hrach! This was supposed to be a peaceful discussion.

@David Grudl: I've done few more experiments and found out that the Composer resolution algorithms are a bit buggy. However I think I have found a reliable way how to define dependencies.

This is a binary relation “satisfy need for” on a set {nette/nette, nette/nette-minified, nette/nette-full}. The key to make the resolution unambiguous is that the relation is partial order.

Here is the packages.json:

{
	"packages": {
		"nette/nette": {
			"2.0.11": {
				"name": "nette/nette",
				"version": "2.0.11",
				"dist": {
					"url": "https://github.com/nette/nette/releases/download/v2.0.11/NetteFramework-2.0.11-PHP5.3.zip",
					"type": "zip"
				}
			}
		},
		"nette/nette-minified": {
			"2.0.11": {
				"name": "nette/nette-minified",
				"version": "2.0.11",
				"dist": {
					"url": "https://github.com/nette/nette-minified/archive/v2.0.11.zip",
					"type": "zip"
				},
				"replace": {
					"nette/nette": "self.version"
				}
			}
		},
		"nette/nette-full": {
			"2.0.11": {
				"name": "nette/nette-full",
				"version": "2.0.11",
				"dist": {
					"url": "https://github.com/nette/nette/releases/download/v2.0.11/NetteFramework-2.0.11-PHP5.3.zip",
					"type": "zip"
				},
				"replace": {
					"nette/nette": "self.version",
					"nette/nette-minified": "self.version"
				}
			}
		}
	}
}

And then in composer.json you will have something like

{
	"require": {
		"nette/nette-minified": "2.0.*",
		"nextras/application": "*"
	},

	"require-dev": {
		"nette/nette-full": "2.0.*"
	},

	"repositories": [
		{
			"type": "composer",
			"url": "https://nette.org/"
		}
	]
}

Note: nextras/application is an example of package which has dependency on nette/nette. The need for nette/nette is satisfied by both nette/nette-minified and nette/nette-full.