Laszlo (Laca) Peter wrote:
On Sun, 2009-05-24 at 14:13 -0500, Shawn Walker wrote:
...
If a hypothetical build system can have more than one source
packages per binary package, they can list multiple values for
source_pkg_fmri.
Ah, ok, that's what I was getting at.
<package name> will be problematic here unless it is escaped. For
example, a package might be named "developer/tool/exuberant-ctags",
which escaped would be 'developer%2Ftool%2Fexuberant-ctags'.
That's a good point. I'm leaning towards keeping the package
name and converting the /-s to directories so if you have a
large number of source packages installed, they are neatly
organised. It's not so nice to deal with esc%61%70ed names
from the command line.
Doing that will be problematic for a different reason though. Namely
only a single package should (and eventually can) deliver the directory
structure, so instead of being able to have each package deliver its own
directory, you will have to have a single master "source package" that
all source packages are dependent on that delivers the entire source
directory structure if *any* of the source packages are installed.
That doesn't seem so nice :|
Also, instead of '-<package version>', I would use the same format that
the FMRI class already provides. As an example:
Thinking about this again, source packages belonging to
different versions of the same upstream package will have
the same name, so you can only install 1 version at any
time. If you need to know the version, you can always
find out with pkg list or pkg info. Which means I can
omit the version altogether and make life easier.
Yes, although including the version number in the directory named would
allow the user to easily install the sources for multiple versions.
However, I have no strong preference here and I think whatever you pick
will be fine :)
src/developer/tool/exuberant-ctags
Isn't this exactly what I have above?
Sorry, I didn't realise that in your example above "src/" was part of
the actual package name since you had listed "/usr/share/src/".
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
