Q about "repackage" or "reinstall"

[patrick keshishian]

I hope someone can point me to the right answer here cause I'm a bit
frustrated right now and probably not looking in the right place for
the answer:)

say you are working on a package that takes "crap load" of hours to
build, so if you get to the very last part of the packaging it up and
installing, but you had a typo, or the like, in your pkg/PLIST, in
@exec, that aborts the installation, how can you force the
re-packaging without having 'make repackage' go through and attempt to
clean every dependency package?

TIA,
--patrick

[kaosagnt]

patrick keshishian wrote:

> I hope someone can point me to the right answer here cause I'm a bit
> frustrated right now and probably not looking in the right place for
> the answer:)
>
> say you are working on a package that takes "crap load" of hours to
> build, so if you get to the very last part of the packaging it up and
> installing, but you had a typo, or the like, in your pkg/PLIST, in
> @exec, that aborts the installation, how can you force the
> re-packaging without having 'make repackage' go through and attempt to
> clean every dependency package?
>
> TIA,
> --patrick
>
>  

If you haven't cleaned out the build area you should just be able to fix
the PLIST, move the already built package out of the packages/{arch}/all
directory and make package again.

Ian McWilliam

[Joachim Schipper-2]

On Fri, Nov 06, 2009 at 05:54:09PM +1100, Ian McWilliam wrote:

> patrick keshishian wrote:
> >I hope someone can point me to the right answer here cause I'm a bit
> >frustrated right now and probably not looking in the right place for
> >the answer:)
> >
> >say you are working on a package that takes "crap load" of hours to
> >build, so if you get to the very last part of the packaging it up and
> >installing, but you had a typo, or the like, in your pkg/PLIST, in
> >@exec, that aborts the installation, how can you force the
> >re-packaging without having 'make repackage' go through and attempt to
> >clean every dependency package?
>
> If you haven't cleaned out the build area you should just be able to
> fix the PLIST, move the already built package out of the
> packages/{arch}/all directory and make package again.

Or use `make clean=package'.

                Joachim

[patrick keshishian]

On Thu, Nov 5, 2009 at 10:54 PM, Ian McWilliam <kaosagnt@...> wrote:

> patrick keshishian wrote:
>>
>> I hope someone can point me to the right answer here cause I'm a bit
>> frustrated right now and probably not looking in the right place for
>> the answer:)
>>
>> say you are working on a package that takes "crap load" of hours to
>> build, so if you get to the very last part of the packaging it up and
>> installing, but you had a typo, or the like, in your pkg/PLIST, in
>> @exec, that aborts the installation, how can you force the
>> re-packaging without having 'make repackage' go through and attempt to
>> clean every dependency package?
>
> If you haven't cleaned out the build area you should just be able to fix the
> PLIST, move the already built package out of the packages/{arch}/all
> directory and make package again.

Thanks for the reply.

I did do that at first (rm-ing the package.tgz files), because I
remember this used to work, but it didn't work this time, so I wonderd
if something might have changed with the -current. But I could've been
doing something wrong -- thinking back to what I was doing, after
removing the package.tgz files I was running `make install' not `make
package' I don't know if that makes any difference.

I'm going to play with a smaller package this weekend; i.e.,g break
PLIST and run through the motions. Just for my sanity.

Cheers,
--patrick

[Marc Espie-2]

On Fri, Nov 06, 2009 at 11:41:07PM -0800, patrick keshishian wrote:

> On Thu, Nov 5, 2009 at 10:54 PM, Ian McWilliam <kaosagnt@...> wrote:
> > patrick keshishian wrote:
> >>
> >> I hope someone can point me to the right answer here cause I'm a bit
> >> frustrated right now and probably not looking in the right place for
> >> the answer:)
> >>
> >> say you are working on a package that takes "crap load" of hours to
> >> build, so if you get to the very last part of the packaging it up and
> >> installing, but you had a typo, or the like, in your pkg/PLIST, in
> >> @exec, that aborts the installation, how can you force the
> >> re-packaging without having 'make repackage' go through and attempt to
> >> clean every dependency package?
> >
> > If you haven't cleaned out the build area you should just be able to fix the
> > PLIST, move the already built package out of the packages/{arch}/all
> > directory and make package again.
>
> Thanks for the reply.
>
> I did do that at first (rm-ing the package.tgz files), because I
> remember this used to work, but it didn't work this time, so I wonderd
> if something might have changed with the -current. But I could've been
> doing something wrong -- thinking back to what I was doing, after
> removing the package.tgz files I was running `make install' not `make
> package' I don't know if that makes any difference.
>
> I'm going to play with a smaller package this weekend; i.e.,g break
> PLIST and run through the motions. Just for my sanity.
>
> Cheers,
> --patrick

You likely have something setup in your env or mk.conf wrt dependency handling,
because I do this all the time without any problem at all...