On 12/15/14, René Rebe <[email protected]> wrote: > Hi, > > On Dec 15, 2014, at 0:15, Barry Kauler <[email protected]> wrote: > >> >> Hi, >> I have created package/archiver/dpkg-deb, which is the same as 'dpkg' >> except I only want to install the 'dpkg-deb' utility. >> >> I want to run configure and make as normal, but want to replace 'make >> install' with my own code, which will just install the 'dpkg-deb' >> utility. >> >> Reading the T2 Handbook, I can see how to use hooks, and have done so, >> with success, however I cannot see how to completely disable the 'make >> install' step and replace with my own code. >> >> Note, I have previously used 'custmain', that works fine, except it is >> for the entire build process. >> >> The solution is probably quite simple! Can anyone advise me? > > > To not run make install, simply clear the makeinstopt: > > makeinstopt=“” > > If you do not want the rest of the dpkg package in your build at all, I > would not create a copy of the package, but simply do the modification to > the dpkg package in your target configuration in: > > target/…/pkg_dpkg_post.conf > > René > > PS: the plan is to remove the old custmain entirely anyways - everything can > be disabled with variables like above, and the rest more elegantly with the > newer hooks. >
Rene, Thanks for the info. Yes, I had just this morning figured out about makeinstallopt='' Actually, I want to build the full dpkg, as well as dpkgd-deb with just the one utility. The reason is that Puppy/Quirky users will have just 'dpkg-deb' in the build of the distro, but the full dpkg is just a few clicks away via the Puppy Package Manager, should they need it. Ah, 'custmain', I have used it a few times. I like it, so don't take it out too soon! There was something curious yesterday, a package that I introduced to my local T2, needed just 'make' and 'make install', so I had no .conf file, but T2 stopped with a compile error. I already tested compiling that pkg in my Quirky built from the packages compiled in T2, so my native environment is identical, and it compiled ok. Anyway, I just created a .conf with custmain and just executed 'make' and 'make install', and it compiled fine in T2. ...so, custmain bypassed something that caused a compile failure. Note, I have been madly adding packages to my local T2, intend to submit them sometime. See my blog: http://bkhome.org/news/?viewDetailed=00134 http://bkhome.org/news/?viewDetailed=00135 Regards, Barry
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
