On Tue, Sep 13, 2011 at 6:32 PM, Yaakov (Cygwin/X) <[email protected]> wrote: > On Tue, 2011-09-13 at 18:45 -0400, Jack wrote: >> New question - if I wan't to keep my own version of a cygport package, >> say just changing some configure parameters, what is the suggested >> change to naming/numbering so I don't conflict with the official >> package? > > As a standalone program, just don't install the Ports package, instead > build from the .cygport file and install into your system (don't forget > to run the postinstall scripts).
Hmm... I have a few personal packages I build with cygport & I have also upgraded some of the Ports packages for personal use (ffmpeg & supporting libraries). After running cygport X-Y-Z.cygport almostall, I copy everything from the dist directory into my /localdistro/release directory & then run genini like so: cd /localdistro/; perl -e 'printf "setup-timestamp: %s\n", time' > setup.time; genini --recursive setup.time release/* > setup.ini; rm setup.time; bzip2 -kc setup.ini > setup.bz2 Then my packages are available when I run setup. I'm not sure when I picked this procedure up, but it's been in my bash history FOREVER :-) Are you saying there's a way to install straight from the .cygport build? Will cygcheck & setup recognize my packages if I install them this way? NT ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
