[Bug 675934] New: api.gnome.org/jhbuild/*
- From: "sysadmin" (bugzilla.gnome.org) <bugzilla gnome org>
- To: gnome-infrastructure gnome org
- Subject: [Bug 675934] New: api.gnome.org/jhbuild/*
- Date: Sat, 12 May 2012 11:25:14 +0000 (UTC)
https://bugzilla.gnome.org/show_bug.cgi?id=675934
sysadmin | Other | unspecified
Summary: api.gnome.org/jhbuild/*
Classification: Infrastructure
Product: sysadmin
Version: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: Other
AssignedTo: sysadmin-maint gnome bugs
ReportedBy: fpeters 0d be
QAContact: sysadmin-maint gnome bugs
GNOME version: ---
Bug 675873 is about moving modulesets out of the jhbuild tree; past experience
in moving modulesets tells us this brings quite a lot of inquiries as jhbuild
stops working on "cannot find moduleset"; it would be nice to avoid this and
the best solution so far is to bless api.gnome.org/something as the place where
modulesets will be, now and forever.
The initial plan was to ask for a hook to copy files from the git module to a
location such as http://api.gnome.org/modulesets/$version/ but now I wonder if
we could simply have http://api.gnome.org/modulesets/$version/gnome.modules as
a static file, that would '<include ...>' the right locations.
This adds an indirection level but would help in case of filename changes.
Do you sysadmin have a preference on this?
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact of the bug.
You are watching the assignee of the bug.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]