You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, any new packages found in brew file init are added in the root Brewfile.
It is useful if it has an option that brew file init adds packages to the branch Brewfile, which is specified by file command in the root Brwefile.
For example, let consider
that you want to share the same Brewfile at several machines,
but some packages are needed for the specific machine.
In this case, with the current brew-file,
you can make the following Brewfile:
...
file Brewfile.$HOSTNAME
and prepare Brewfile.machine1, with the content like:
brew package_only_for_machine1
Then you can install packages by brew file install in all machines,
and package_only_for_machine1 is installed only in the machine1.
But you need to add or modify Brewfile and Brewfile.machine1 manually when you add new packages.
Otherwise, if you execute brew file init, these packages will be added in the root Brewfile.
Therefore, it is good to have another command of file, like main_file.
If you have the root Brewfile like:
...
main_file Brewfile.$HOSTNAME
then brew file init will add new packages in Brwefile.$HOSTNAME if it is exists otherwise in the root Brewfile.
Maybe it is better to have an option to select the root or the main Brewfile for brew file init (and wrapped brew install command).
The text was updated successfully, but these errors were encountered:
move brewinfo to ext
remove main brewinfo from brewinfo_ext
DONE
--
At initialize, put read list to main brewinfo's list
cleanup: remove non-existing packages from all brewinfos, remove packages from main list if they are in other ext brewinfo. remain all tap list in main brewinfo in any case
DONE
--
Make main file if it does not exist
->
If any packages are included in the file, the file is created.
About main, it has at least some taps, then it is created in any case
Currently, any new packages found in
brew file init
are added in the root Brewfile.It is useful if it has an option that
brew file init
adds packages to the branch Brewfile, which is specified byfile
command in the root Brwefile.For example, let consider
that you want to share the same Brewfile at several machines,
but some packages are needed for the specific machine.
In this case, with the current brew-file,
you can make the following Brewfile:
and prepare Brewfile.machine1, with the content like:
Then you can install packages by
brew file install
in all machines,and
package_only_for_machine1
is installed only in the machine1.But you need to add or modify Brewfile and Brewfile.machine1 manually when you add new packages.
Otherwise, if you execute
brew file init
, these packages will be added in the root Brewfile.Therefore, it is good to have another command of
file
, likemain_file
.If you have the root Brewfile like:
then
brew file init
will add new packages inBrwefile.$HOSTNAME
if it is exists otherwise in the root Brewfile.Maybe it is better to have an option to select the root or the
main
Brewfile forbrew file init
(and wrappedbrew install
command).The text was updated successfully, but these errors were encountered: