> Certainly theoretically possible. Using sqlite directly would be fragile
> with respect to the db schema changing though.
The schema can always be checked prior to installing: if mismatched, skip it or
fail.
smime.p7s
Description: S/MIME cryptographic signature
__
On 2011-4-11 01:36 , Jeremy Lavergne wrote:
> For those that know the backend better, is there any chance we can have
> MacPorts create an sqlite script to "install" into macports whatever is
> installed from a MacPorts-produced [m]pkg?
>
> I assume it would function like a postflight script.
C
> I'm having a little difficulty parsing just what exactly that means. :)
>
> Are you saying that what's in trunk will now unpack directly into the
> ${prefix} and ignore the
> ${prefix}/var/macports/software/${name}/${version}_${revision}+${variants}
> location entirely? If true, that would l
On Apr 10, 2011, at 12:01 PM, Jeremy Lavergne wrote:
> Now that images and archives is in trunk, instead of hardlinking files into
> place it's just expanding the archive into place--or at least that's what it
> looks like. I've given up on it for now, unmerging it in my local trunk.
I'm havin
On Sun, Apr 10, 2011 at 2:29 PM, Ryan Schmidt wrote:
>
> On Apr 7, 2011, at 13:45, Felipe Tanus wrote:
>
> > On Thu, Apr 7, 2011 at 4:29 AM, Anders F Björklund wrote:
> >> Why did you rename the program from "pkg" to "macpkg" ?
> >
> > To get sued by apple :-)
> > Just kidding,
>
> You probably wo
On Apr 10, 2011, at 14:05, Jeremy Lavergne wrote:
>> py25-cheetah: update to 2.4.4 and append python version number to program
>> names, like the other py*-cheetah ports already do; see #28522
>
> Does PortGroup python25 also have `python.link_binaries` available?
>
> I think that might simpli
> py25-cheetah: update to 2.4.4 and append python version number to program
> names, like the other py*-cheetah ports already do; see #28522
Does PortGroup python25 also have `python.link_binaries` available?
I think that might simplify your appending loop.
smime.p7s
Description: S/MIME crypt
> Well it's more complicated than that. The packages produced by MacPorts only
> install into their ${prefix}. They don't install into
> ${prefix}/var/macports/software/${name}/${version}_${revision}+${variants}
> and then hardlink into ${prefix} like MacPorts does when it installs things.
> Th
Ryan Schmidt wrote:
>>> You're suggesting this as a solution for the problem that packages produced
>>> by MacPorts interfere with MacPorts?
>>
>> Essentially.
>
> Well it's more complicated than that. The packages produced by MacPorts only
> install into their ${prefix}. They don't install in
On Apr 10, 2011, at 1:36 PM, Jordan K. Hubbard wrote:
>
> On Apr 7, 2011, at 1:03 PM, Jeff Johnson wrote:
>
>> So is MacPorts prepared to commit to a UUID based identification scheme for
>> ports?
>
> Evidently not. :)
>
No biggie: I'll roll my own UUIDv3/UUIDv5 scheme under the "http://rpm
On Apr 7, 2011, at 1:03 PM, Jeff Johnson wrote:
> So is MacPorts prepared to commit to a UUID based identification scheme for
> ports?
Evidently not. :)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailm
On Apr 10, 2011, at 12:23, Jeremy Lavergne wrote:
>> You're suggesting this as a solution for the problem that packages produced
>> by MacPorts interfere with MacPorts?
>
> Essentially.
Well it's more complicated than that. The packages produced by MacPorts only
install into their ${prefix}.
On Apr 7, 2011, at 13:45, Felipe Tanus wrote:
> On Thu, Apr 7, 2011 at 4:29 AM, Anders F Björklund wrote:
>> Why did you rename the program from "pkg" to "macpkg" ?
>
> To get sued by apple :-)
> Just kidding,
You probably won't:
http://www.apple.com/legal/trademark/guidelinesfor3rdparties.htm
> You're suggesting this as a solution for the problem that packages produced
> by MacPorts interfere with MacPorts?
Essentially.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
h
On Apr 10, 2011, at 10:36, Jeremy Lavergne wrote:
> For those that know the backend better, is there any chance we can have
> MacPorts create an sqlite script to "install" into macports whatever is
> installed from a MacPorts-produced [m]pkg?
>
> I assume it would function like a postflight sc
For those that know the backend better, is there any chance we can have
MacPorts create an sqlite script to "install" into macports whatever is
installed from a MacPorts-produced [m]pkg?
I assume it would function like a postflight script.
smime.p7s
Description: S/MIME cryptographic signature
16 matches
Mail list logo
