Cross package maker. DEB/RPM generation or conversion. Derived from jordansissel/fpm.

⌈⌋ branch:  cross package maker


Check-in [d9ca0cb590]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
SHA1 Hash:d9ca0cb590489953ec58d429f2aa4ab9bfe64c51
Date: 2014-11-21 17:43:45
User: jls
Comment:Add note about Code of Conduct Huge thanks to everyone involved in contributor-covenant.org for providing this framework. <3
Tags And Properties
  • branch=trunk inherited from [5980cef12a]
  • sym-trunk inherited from [5980cef12a]
Context
2014-12-10
22:37
[f464393ebb] Merge pull request #824 from dlanderson/patch-2 Remove errant space in debian postinst_upgrade.sh (user: jls, tags: trunk)
21:37
[d94f8d5b37] Remove errant space in debian postinst_upgrade.sh This space was preventing postinst scripts to run on initial install of the .deb package (user: dave, tags: trunk)
2014-11-21
17:43
[d9ca0cb590] Add note about Code of Conduct Huge thanks to everyone involved in contributor-covenant.org for providing this framework. <3 (user: jls, tags: trunk)
17:43
[374c5fa262] Add a Code of Conduct from http://contributor-covenant.org/ (user: jls, tags: trunk)
Changes

Changes to README.md.

148
149
150
151
152
153
154




155
156
157
158
159
160
161
...
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
  request. If you don't know git, I also accept diff(1) formatted patches -
  whatever is most comfortable for you.
* Want to lurk about and see what others are doing? IRC (#fpm on
  irc.freenode.org) is a good place for this as is the 
  [mailing list](http://groups.google.com/group/fpm-users)

### Contributing by forking from GitHub





First, create a github account if you do not already have one.  Log in to
github and go to [the main fpm github page](https://github.com/jordansissel/fpm).

At the top right, click on the button labeled "Fork".  This will put a forked
copy of the main fpm repo into your account.  Next, clone your account's github
repo of fpm.  For example:
................................................................................
At this point, the fpm command should run directly from the code in your cloned
repo.  Now simply make whatever changes you want, commit the code, and push
your commit back to master.

If you think your changes are ready to be merged back to the main fpm repo, you
can generate a pull request on the github website for your repo and send it in
for review.


##Problems running bundle install?

If you are installing on Mac OS 10.9 (Mavericks) you will need to make sure that 
you have the standalone command line tools seperate from Xcode:

    $ xcode-select --install







>
>
>
>







 







<







148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
...
190
191
192
193
194
195
196

197
198
199
200
201
202
203
  request. If you don't know git, I also accept diff(1) formatted patches -
  whatever is most comfortable for you.
* Want to lurk about and see what others are doing? IRC (#fpm on
  irc.freenode.org) is a good place for this as is the 
  [mailing list](http://groups.google.com/group/fpm-users)

### Contributing by forking from GitHub

Please note that this project is released with a Contributor Code of Conduct.
By participating in this project you agree to abide by its terms. See
the [CODE\_OF\_CONDUCT.md](CODE_OF_CONDUCT.md).

First, create a github account if you do not already have one.  Log in to
github and go to [the main fpm github page](https://github.com/jordansissel/fpm).

At the top right, click on the button labeled "Fork".  This will put a forked
copy of the main fpm repo into your account.  Next, clone your account's github
repo of fpm.  For example:
................................................................................
At this point, the fpm command should run directly from the code in your cloned
repo.  Now simply make whatever changes you want, commit the code, and push
your commit back to master.

If you think your changes are ready to be merged back to the main fpm repo, you
can generate a pull request on the github website for your repo and send it in
for review.


##Problems running bundle install?

If you are installing on Mac OS 10.9 (Mavericks) you will need to make sure that 
you have the standalone command line tools seperate from Xcode:

    $ xcode-select --install