On Thu, Oct 30, 2014 at 07:52:51AM -0700, Nick Rogers wrote:
> On Wed, Oct 29, 2014 at 5:44 PM, Baptiste Daroussin
> wrote:
>
> > On Wed, Oct 29, 2014 at 01:43:27PM -0700, Nick Rogers wrote:
> > > On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin
> > > wrote:
> > >
> > > > On Wed, Oct 29, 2014
On Wed, Oct 29, 2014 at 5:44 PM, Baptiste Daroussin
wrote:
> On Wed, Oct 29, 2014 at 01:43:27PM -0700, Nick Rogers wrote:
> > On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin
> > wrote:
> >
> > > On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote:
> > > > Hello,
> > > >
> > > > I am
On Wed, Oct 29, 2014 at 01:43:27PM -0700, Nick Rogers wrote:
> On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin
> wrote:
>
> > On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote:
> > > Hello,
> > >
> > > I am in the process of upgrading some proprietary software that has
> > always
>
On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin
wrote:
> On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote:
> > Hello,
> >
> > I am in the process of upgrading some proprietary software that has
> always
> > been deployed via a "custom" package created by the old pkg_create. So
> fa
On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote:
> Hello,
>
> I am in the process of upgrading some proprietary software that has always
> been deployed via a "custom" package created by the old pkg_create. So far
> I've been able to use "pkg create" to achieve what I want, but it seem
Hello,
I am in the process of upgrading some proprietary software that has always
been deployed via a "custom" package created by the old pkg_create. So far
I've been able to use "pkg create" to achieve what I want, but it seems
that the "requirements" script is no longer a part of the new pkg
fra
