Hi, On 2017-09-25 08:10 AM, Chris Rees wrote: > On 2017-09-25 05:54, Kubilay Kocak wrote: >> On 9/25/17 6:16 AM, Helen Koike wrote: >>> Hi, >>> >>> According to >>> https://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html >>> , I need to add a @sample macro in pkg-plist to add a configuration >>> file. >>> >>> But I am also using USE_PYTHON= autoplist in my Makefile, so I don't >>> have the pkg-plist file. >>> >>> Should I remove autoplist and generate the pkg-plist by hand? Or is >>> there another way to do this? >>> >>> I'll need this to update the version of the package >>> sysutils/py-google-compute-engine. >>> >>> Thanks >>> Helen >> >> Hi Helen, >> >> As far as I'm aware, autoplist, PLIST_* definitions and pkg-plist >> entries can be used cumulatively (in combination with each other) to >> produce a correct and complete installed files lis>>
Thanks, I didn't know that. > > Careful doing that! If you do, you may find the sample file gets listed > twice, or worse the actual config file gets listed. > > If you want to view the final generated plist then in the normal ports > directory: > > % make package > % less `make -VTMPPLIST` Awesome, thanks a lot. > > (those are backticks). > > It's probably harmless to have a file listed twice, but if you list the > actual config file it gets blown away on each update. > > Cheers, > > Chris > Helen _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
