# use ansible command machine as packager

**URL:** <https://forum.ansible.com/t/use-ansible-command-machine-as-packager/13629>\
**Category:** Ansible Project\
**Created:** [October 8, 2013, 1:33pm UTC](https://forum.ansible.com/t/use-ansible-command-machine-as-packager/13629 "2013-10-08T13:33:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jerome\_Wagner](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@Jerome\_Wagner](https://forum.ansible.com/u/Jerome_Wagner)\
**Post date:** [October 8, 2013, 1:33pm UTC](https://forum.ansible.com/t/use-ansible-command-machine-as-packager/13629/1 "2013-10-08T13:33:35Z")

</div>

Hello,

I would like to use ansible to create/prepare packages (yum packages, .tgz files, …) before they are deployed to other hosts.

do you think it is a good idea to have 127.0.0.1 in the inventory and target this host with a packager play ?

I am interested in knowing how others are solving their packaging needs

Thanks  
Jerome

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [October 8, 2013, 3:08pm UTC](https://forum.ansible.com/t/use-ansible-command-machine-as-packager/13629/2 "2013-10-08T15:08:13Z")

</div>

It’s fine to put localhost in inventory, just be sure you don’t ever address the “all” group and instead select a group of hosts that describe what you want to manage.

We have an open pull request to make localhost implicit in inventory just for plays that say “hosts: localhost” so you don’t even have to add this.