Compare to Features module

yes, there seems almost a complete overlap when just looking at the description.

Could you please explain the differences between this module and features module?

An expression comes to mind: same, same, but different.

Comparison won't help you understand; differences are not what something is. If you'd like to understand both modules without comparing them, you could try and learn about both: how they work, what are their strengths and weaknesses, etc.

In the case of package_builder, I would suggest to read the code, dissect the output of a package, and/or try to use/reuse a package. These are helpful strategies, imho.

It will still be easier if you can provide some documentation on the differences. Many people know (and love) features. I need a compelling reason to try package_builder - and by reading a comparison, I might find such a reason.

Different is only good if there's a reason for the difference.

I did read the code. All I could find was a lack of coding standards.

Also, why does the 6.x branch start with alpha 2? where is alpha 1?

I would be very impressed if you managed to make a "package builder" in 1 day (5 commits, the 5.x branch can be ignored as it has absolutely nothing in common with the 6.x branch) that replaces what the features module did in one year (over 350 commits).

I would say the biggest difference is the usage of save function instead of default hooks, like features does it.

Comparison won't help you understand; differences are not what something is. If you'd like to understand both modules without comparing them, you could try and learn about both: how they work, what are their strengths and weaknesses, etc.

This can be translated into: You don't know either, and you didn't even care to search for existing solutions before scratching your own itch.

In addition to flobruit's and dereine's findings:

- Abuses nodes as entity and storage for "packages".

- Only supports a small range of other contributed modules in uncertain versions.

- Contains various security issues.

Okay.. I acquiesce. Please make a point to keep this issue civil and constructive; I'll try to be as helpful as possible with questions about how they compare. If there are any bugs to file, filing them separately will help us develop the module.

In reference to the 'exporting site functionality to code' ecosystem, I've spoken to a number of people that are interested in this design and have offered to help flesh it out. If you want to use features, by all means, use features. We will continue working toward solving the site functionality in code issue, as it is very important to us as well.

Here's a rundown of what I have about package builder:
- Emphasis is on simplicity. (It has a much smaller codebase.)
- No included diff/comparison support (when you re-export a package, you can use cvs, svn, git, bzr, hg, etc to view diffs)
- More readable output (each exported component is in an individual file sorted by type in a specific folder). This makes it a lot easier to understand Drupal entirely in code.
- No internal roll back. You can reinstall an older version of the package using your version control software.
- No included module management interface other than admin/build/modules for installation and removal.
- Currently, our ui is less developed.

I would say the biggest difference is the usage of save function instead of default hooks, like features does it.

We're looking at adding an option to the ui for users to make a choice between default hooks and saving to the database.

uh ok, so yeah overlap... I went to a couple of seriously heated BOF's about deployment/package management...

From the perspective of a sitebuilder the term "Feature(s)" doesn't exactly equate to "manage my sites configuration" in code.

"Package management" seems attractive because it seems that i could manage most of my configuration just by checking a crap load of boxes, and putting it all in SVN. If features does this too, its not exactly sold as such in the docs (i missed the session)...

Security issues and saving nodes as entities aside, so far this module (PM) doesn't quite work for me, i'm getting an error about the package being modified by another user, grr...