Re: guidelines for go?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 29, 2013 at 12:12:02PM -0400, Vincent Batts wrote:
> >So, is that example what we should follow if we have some libraries we'd
> >like to package up now? (Should these basically only generate -devel
> >subpackages?) Is it okay to review it copying your basic idea now but with
> >the caveat that we'll update if we get closer to what you want to get to?
> golang libraries are basically -devel packages, not just subpackages.
> The part that is going to need revision is how to handle that fact that
> any given library, should provide subpackages for all the arch's of *.a,
> that can be installed individually or exist together.

It looks like the Haskell guidelines address this by making the packages not
produce -devel subpackages but instead have a provides line like this:

  Provides: golang-%{pkg_name}-devel = %{version}-%{release}


-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm@xxxxxxxxxxxxxxxxx>
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging





[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux