On 08/21/12 11:30 AM, Brock Pytlik wrote:
On 08/20/12 16:03, Tim Foster wrote:
On 08/21/12 10:12 AM, Brock Pytlik wrote:
On 08/17/12 16:23, Tim Foster wrote:
https://cr.opensolaris.org/action/browse/pkg/timf/pkglint-legacy/pkglint-legacy-webrev/
Sorry I should've been clearer. What happens if we have:
legacy pkg=foo/bar
? Like I said, maybe we just don't care for now cause our legacy
packages can never be named like that? I guess I was thinking of what
this might look like if we had other packaging systems as legacy.
[snip]
I understand. If in the future we produce a legacy action that covers a
new packaging type, we probably ought to declare what types of dummy
package entry we should create for each legacy action.
As is, installing a legacy action containing a '/' character results in
a rather odd pkginfo file being created in
/var/sadm/pkg/foo/bar/pkginfo, which of course can't be supported in SVR4.
timf@kura[335] pkginfo foo/bar
ERROR: information for "foo/bar" was not found
I'll file an RFE - pkglint really ought to check for these today, but
not this putback.
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
